Skip to main content

Android developer moving to iOS - What do I need to know?



I'm interested in starting developing on the iOS platform, after a couple of years of Android work. What are the main things that are likely to trip me up when designing/coding for iOS instead of Android?





Source: Tips4all

Comments

  1. I have done some iphone apps after doing Android.


    Objective-c is just another language; not at all hard to learn.
    Understand how iPhone memory works. How the ref count and AutoreleasePools stack works. This should be the most important thing to learn.
    You will love the interface builder. Creating a new screen for the iPhone is much easier.
    iPhone's version of the Android ListView is called a TableView. More or less the same but you need to define an amount of sections.
    I love how iPhone devs use the Delegate pattern, I am using it in Android now. Pay attention to that.
    Resources can have their own folders. For example: A drawable can be in /car/model/drawable
    Adding animation to iphone objects is VERY easy. You will notice that a lot of methods have a last parameter with BOOL animated.
    Creating custom components is easier.


    Things that made me lose a lot of time:


    You can send msgs to NIL.
    Logs are not as friendly as Android's.
    You need to add every file to the project. It's not just putting it in the correct place.
    Updates to the env means downloading 2GB every time.
    When printing logs with NSLog, NSString needs to use %@ not %s.
    Xcode has some strange behavior. The cursor moves around your screen.
    Merging commits in iPhone source is hard. The project file and the xibs always get conflicts.

    ReplyDelete
  2. I just want to say that Dont use Interface Builder, Try to make application through coding
    with this you will easily catch the building process for IPhone program.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex