Use this Google post to start development for Android!
Key UI paradigms in Android:
- Action bar,
- Overflow menu,
- Back button: back button pop activity from main OS stack.
- Share action,
Key differences with iOS:
- No need for class prefix
- Ivars start with m, not _
- Have to check NULL
- No Properties
Project Structure:
Android applications primarily has 2 sections:
- Java Source-code:
- Activities: (like UIViewControllers). Android OS keeps a main application’s activity stack – when 1 app launched -> main activity of that app is pushed on stack. (Many apps can be launched and so pushed on the same stack). Back button pops from OS stack -> can pop different applications.
- Activities can be created with Intents (like UIViewController with custom init). Activities can also return data -> placing data on the Intents.
- Any activity can be Entrance for application if registered in AndroidManifest.
- To be sent between intents & fragments, objects have to implement Parcelable interface. (like NSCopying protocol in iOS)
- Fragments: (since Android 3.0) mini controllers that can be instantiated to fill activities (like subviews). Use many fragments on an activity!
- Views:
- Adapters,
- Data (models and managers).
- Activities: (like UIViewControllers). Android OS keeps a main application’s activity stack – when 1 app launched -> main activity of that app is pushed on stack. (Many apps can be launched and so pushed on the same stack). Back button pops from OS stack -> can pop different applications.
- Resource (res folder)
- Images
- XML Layout files: like xib files
- XML Values files: like plist
- AndroidManifest.xml (similar to
Project-Info.plist)
- Store activities, app names and Intents