DevFest Sul 2014 - Android 4 lazy iOS Devs
•Transferir como PPTX, PDF•
2 gostaram•584 visualizações
This document provides an overview of key differences between iOS and Android development for iOS developers looking to learn Android development. It summarizes UI paradigms like the action bar and overflow menu in Android. It also covers differences in project structure, activities versus view controllers, fragments, data storage options, layouts, and publishing apps to Google Play Store which has lower fees than the Apple App Store.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Semelhante a DevFest Sul 2014 - Android 4 lazy iOS Devs
Semelhante a DevFest Sul 2014 - Android 4 lazy iOS Devs (20)
Mais de Jackson F. de A. Mafra
Mais de Jackson F. de A. Mafra (20)
Último
Último (6)
DevFest Sul 2014 - Android 4 lazy iOS Devs
- 1. Give yourself to the Dark Side! Jackson F. de A. Mafra
- 3. Understand some of the key UI paradigms in use on Android today: the action bar, the overflow menu, the back button, the share action, and more.
- 4. No More Menu Button
- 5. New Buttons
- 7. Navigation
- 8. ActionBar
- 9. ActionBar
- 10. MultiPane
- 11. Dialogs
- 12. Android is not iOS
- 13. Android is not iOS
- 14. IDE Android Studio or (Eclipse ADT plugin)
- 15. Android SDK and AVD Manager
- 16. Language Application Structure There are many differences between Objective-C and Java
- 17. Java Say what you will about Java, in the end it's just another language. Be thankful there is no J2EE in sight.
- 18. Language Application Structure Referencing this.object will not call your custom getter. You must use this.getObject.
- 19. Language Application Structure Java methods are typically written as actions or queries, such as getCell(), instead of cellForRowAtIndexPath:.
- 20. Simulator I used to think the iOS simulator was painful, now I realise it's pretty awesome. Skip the Android simulator all together and deploy to a real device, or be prepared to spend a lot of time waiting. Consider to use Genymotion, a fastest Android emulator for app testing and presentation.
- 21. Project Structure Android applications are primarily broken into two sections, the first of which is the Java source code.
- 22. Project Structure The source code is structured via the Java package hierarchy, and it can be structured as you please. However, a common practice is to use top-level categories for activities, fragments, views, adapters, and data (models and managers).
- 23. Project Structure The second major section is the res folder, short for ‘resource’ folder.
- 24. Project Structure The res folder is a collection of images, XML layout files, and XML value files that make up the bulk of the non-code assets.
- 25. Project Structure Android uses Layouts which are xml. They are completely independent from each other. Android Studio also has a nice WYSIWYG editor
- 26. Project Structure On iOS, images are either @2x or not, but on Android there are a number of screen density folders to consider.
- 27. Project Structure Android uses folders to arrange images, strings, and other values for screen density.
- 28. Project Structure One last correlation in project structure is the AndroidManifest.xml file.
- 29. Project Structure This file is the equivalent of the Project-Info.plist file on iOS, and it stores information for activities, application names, and set Intents (system-level events) that the application can handle.
- 30. Activities Activities are the basic visual unit of an Android app, just as UIViewControllers are the basic visual component on iOS.
- 31. Activities Instead of a UINavigationController, the Android OS keeps an activity stack that it manages.
- 32. Activities In essence, the activity lifecycle is very similar to the UIViewController lifecycle.
- 33. Activities
- 34. Fragments The Fragment concept is unique to Android and came around somewhat recently in Android 3.0 (2010).
- 35. Fragments Fragments are mini controllers that can be instantiated to fill activities.
- 36. Fragments Also note that fragments do not have their own contexts and they rely heavily on activities for their connection to the application’s state.
- 37. Fragments Tablets are a great fragment use case example: you can place a list fragment on the left and a detail fragment on the right.
- 38. Fragments Fragments allow you to break up your UI and controller logic into smaller, reusable chunks.
- 39. List Views and Adapters ListViews are the closest approximation to UITableView on Android, and they are one of the most common components that you will use.
- 40. List Views and Adapters Like UITableView has a helper view controller, UITableViewController, ListView also has a helper activity, ListActivity, and a helper fragment, ListFragment.
- 41. List Views and Adapters On Android we don’t have datasources and delegates for ListView.
- 42. List Views and Adapters We have adapters. Adapters come in many forms, but their primary goal is similar to a datasource and table view delegate all in one.
- 43. List Views and Adapters Adapters take data and adapt it to populate a ListView by instantiating views the ListView will display
- 44. AsyncTasks In place of Grand Central Dispatch on iOS, on Android we have access to AsyncTasks.
- 45. AsyncTasks AsyncTasks is a different take on exposing asynchronous tools in a more friendly way.
- 46. Layout The primary structure that you will deal with will be subclasses of ViewGroup – RelativeLayout, LinearLayout, and FrameLayout are the most common.
- 47. Layout Always work in dp (density-independent pixels) instead of pixels directly.
- 48. Data The Data Storage Options available on Android are also very similar to what is available on iOS
- 49. Data Shared Preferences <-> NSUserDefaults
- 50. Data Saving to and fetching from file structure via the internal or external file storage <-> saving to the documents directory
- 51. Data SQLite <-> Core Data
- 52. Data Android offers straight access to the SQLite database and returns cursor objects for results
- 53. IBOutlet If you are anything like me you forget to connect IBOutlets at least 50% of the time every time.
- 54. IBOutlet With Android every view/component has a unique ID, something like: @+id/myButton Button button = (Button)findViewById(R.id.myButton);
- 55. NSLog Log seems to be the go to solution here, you can specify debug, verbose etc. System.out.println(..) also seems to do the job.
- 56. Paid Apple $99 developer fee x Paid Google $25 developer fee
- 57. $25 fee in Play Store. 75% cheaper than Apple's yearly fee.
- 58. Payments handled through Google Checkout.