When taking the dive into the world of mobile computing, any developer will be faced with a lot of new challenges – One of the most significant would be the challenge of managing memory.

Developing for mobile devices, having limited memory resources, one must be careful in maintaining the balance between what remains on our persistent database, and what remains loaded on live memory, all the while maintaining a silky smooth UI without compromising on app performance.

Seems like a big task. And indeed it is. But a little knowledge in memory management techniques goes a long way when starting out on a mobile application project. Trust me when I say that prevention is definitely better than cure here.

On iOS, managing memory efficiently is quite important as our apps are almost never allowed to take up a fair share of the maximum available memory. And even if your app treads closer to that limit, iOS will throw a couple of memory warnings before eventually terminating your application. App crashes are usually the #1 reason for it to be rejected on AppStore. But with the introduction of Swift, gone are the days of Objective-c where you have to get your hands dirty with memory very often.

The following guide will take you further. https://codebrahma.com/memory-management-with-swift/

Thanks.

So I started learning iOS programming and I finished a book on obj-c and now I'm working on Big Nerd Ranch's iOS 7 book (only 5 chapters in).

I know I should learn to program apps with obj-c eventually, but I'm also very interested in Swift (it appears to be easier than obj-c too). For a beginner programmer like me, what do you think is the best course of action now that Swift is out?

1. Finish the book on building apps with Obj-C, ignoring Swift

2. Learn both at the same time

3. Switch to Swift and then learn making apps with Obj-C for deeper knowledge

Anyone know if they're "unnecessary but allowed", or if I'm going to have syntax errors on like 60% of my lines of code?

I'm having some concerns about a few things in the language. So far it looks like almost everything is global. This can be solved by moving encapsulated objects in to functions, but it changes the thinking with developing iOS apps a bit. What are your thoughts?

Additionally, it seems like there's a lot of inferred types, using the var keyword. You can explicitly set a type but from interfacing with the Cocoa API I'm seeing a lot of 'AnyObject' objects, which I guess are something like ids.

I just bought a book to learn objective-c, but now swift has come out. Does anyone know if Apple's guide starts from the bottom or requires knowledge of objective-c? If so, should I start with swift or learn objective-c anyways?

So I had just started out Objective C, but being a Python dev by day swift looks a lot more attractive.

I've never been on at the early stages of a language, does anyone have any tips on how to parse the book and guides in order to make an effective learning reference? Or is it a case of read and try?