Mobile appsdevelopment
- 2. Types of Mobile Applications There are different types of Mobile applications – Native Applications – Hybrid Application – Progressive Web Applications (PWAs) We are going to Talk only about Native applications today….
- 3. Mobile Application Platforms Major Mobile OS – iOS – Android – Windows (Dying soon L)
- 4. Development tools • iOS – Xcode – Appcode • Android – Android Studio – IntelliJ IDEA – Eclipse (Not used much anymore)
- 10. iOS Info.plist
- 14. Android Key components The basic components of any android application are the following: • Activities – Basic component of most applications – Most applications have several activities that start each other as needed – Each is implemented as a subclass of the base Activity class • Broadcast receivers – Receive and react to broadcast announcements • Services – Runs in the background indefinitely – You can bind to a an existing service and control its operation • Content Providers – Makes some of the application data available to other applications – It’s the only way to transfer data between applications in Android (no shared files, shared memory, pipes, etc.) – Other applications use a ContentResolver object to access the data provided via a ContentProvider
- 17. Views • View objects are used specifically for drawing content onto the screen of an Android device. – Display Views • TextView, ImageView – Input and controls • Button, EditText, Switch, CheckBox etc. – Adapter based views • ListView, GridView, RecyclerView
- 18. ViewGroups ViewGroups • Used to contain other View and ViewGroup. • Used for creating a hierarchy of View objects • ViewGroup objects can be instantiated in the same way as standard View items in XML or in Java code.
- 19. ViewGroups • Relative Layout: is a ViewGroup that displays child views in relative positions • Linear Layout: is a ViewGroup that aligns all children in a single direction, vertically or horizontally • Frame Layout: is a placeholder on screen that is used to display a single view • Constraint Layout: is a ViewGroup which allows you to position and size widgets in a flexible way. • ScrollView: An extension of the FrameLayout, the ScrollView class handles scrolling its child objects on the screen. • ViewPager: Used for managing multiple views while only displaying one at a time. • RecyclerView • CoordinatorLayout: The CoordinatorLayout class uses a Behavior object to determine how child View items should be laid out and moved as the user interacts with your app.
- 20. Recycler View • What is RecyclerView? – The RecyclerView widget is a more advanced and flexible version of ListView. • Why RecyclerView? – RecyclerView is a container for displaying large data sets that can be scrolled very efficiently by maintaining a limited number of views. • When you should use RecyclerView? – You can use the RecyclerView widget when you have data collections whose elements changes at runtime based on user action or network events.
- 21. RecylerView
- 22. RecylerView
- 23. Constraint Layout • Allows to make large complex layouts with a flat view hierarchy. • No Nested view groups • More flexible compared to Relative layout.
- 28. Android Navigation • Refers to the interactions that allow users to navigate across, into, and back out from the different pieces of content within the app. • Helps developers to implement navigation, from simple button clicks to more complex patterns, such as app bars and the navigation drawer. • Also ensures a consistent and predictable user experience by adhering to an established set of principles.
- 29. Navigation Component Consists of three major parts: • Navigation graph: – An XML resource that contains all navigation-related information in one centralized location. – includes all of the individual content areas within the app, called destinations, as well as the possible paths that a user can take through the app. • NavHost: – An empty container that displays destinations from navigation graph. – Navigation component contains a default NavHost implementation, NavHostFragment, that displays fragment destinations. • NavController: – Manages app navigation within a NavHost. – Orchestrates the swapping of destination content in the NavHost as users move throughout the app.
- 30. Navigation Graph
- 31. Benefits of Navigation Component The Navigation component provides a number of other benefits, including the following: • Handling fragment transactions. • Handling Up and Back actions correctly by default. • Providing standardized resources for animations and transitions. • Implementing and handling deep linking. • Including Navigation UI patterns, such as navigation drawers and bottom navigation, with minimal additional work. • Safe Args - a Gradle plugin that provides type safety when navigating and passing data between destinations. • ViewModel support - you can scope a ViewModel to a navigation graph to share UI-related data between the graph's destinations.
- 34. Major Components iOS • ViewController • View • NavigationController • TabController • UITableView • UICollectionView • AlertController
- 36. Navigation iOS
- 40. iOS Storyboard
- 41. Grand Central Dispatch GCD is a low-level API for managing concurrent operations. DispatchQueue: • Concurrent: starting multiple tasks at the same time, but doesn’t guarantee for the finish at same time. Tasks can finish in any order. • Serial: executing one task at a time. • Sync: When a work item is executed synchronously with the sync method, the program waits until execution finishes before the method call returns. • Async: executes asynchronously with the async method, the method call returns immediately.
- 42. Grand Central Dispatch • Global Queue: Used to perform non-UI work in the background. • Main Queue: Used to update the UI after completing work in a task on a concurrent queue. Dispatch Queue Priority: – .userInteractive – . userInitiated – .default – .utility – .background – .unspecified
- 43. Examples Perform background Quality of Service (QOS) task - DispatchQueue with delay - Dispatch Groups -
- 45. Common Mistakes • Monolithic views • Business logic inside custom views • Neglecting UI in code reviews
- 47. Dependency Manager • iOS – CocoaPods – Swift Package Manager – Carthage • Android – Gradle – Maven
- 48. Build Variants/Scheme Build Type – Debug – Release Build Flavors: A flavor is used to specify custom features. For example, if production code is slightly different than development code. The combination of Build Type and Flavor is known as Build Variant. For example, for above build types (debug and release) and product flavours (free and paid versions), build variants can be freeDebug, freeRelease, paidDebug, paidRelease.
- 49. Some Features • Push Notification • In App purchase • Camera • Maps
- 50. Native Development Pros – They are very fast and responsive because they are built for that specific platform. – They have the best performance. – They are more interactive, intuitive and run much smoother in terms of user input and output. Cons – They are considerably more expensive to develop compared to cross-platform and web applications. – They require more time to develop as one application has to be written in different languages for different platforms. – They have a higher cost of maintenance and pushing out updates, due to multiple source code bases.
- 51. Hybrid Development Pros – Adaptable to multiple platforms, as the same code can be re-used for Android, iOS, and Windows. – Unified and less expensive development, as the app only has to be developed once using one code base. – Faster development time when compared to native apps as only one development process is involved. Cons – Slower app performance when compared to Native Apps, because the hybrid framework acts as a bridge to communicate with the phone’s native features. – Apps with heavy animations and sound effects aren’t as seamless as their native counterparts.
- 52. Progressive Web Apps Development Pros – Easy to build. – Easy to maintain. – Works offline and performs well on low-quality networks. – Build one app for all platforms — iOS, Android, etc. as long as it can run a browser. Cons – Needs a browser to run. Users have to take another step to type in the URL of the app which amounts to a poor user experience. – Web apps are less interactive and intuitive than native apps.
- 53. Language Preference • Swift for iOS • Kotlin for Android
- 54. Something To Think • I don't have an app on play-store, what should I focus on? • I do have apps on the play-store, what next I should focus on? • Does having an app on play-store gives me an edge over other candidate on the Interview-board? • What do to when we are stuck?? • Which to choose, iOS or Android? • Why to choose both and becoming expert on one?
- 55. Android Useful Links • Android Jetpack • Android Manifest • Android Navigation • Developing Android Apps with Kotlin • Common Architectural principles • Android Developer Guide
- 56. iOS Useful Links • swift.org • Swift Documentation • Appcoda • Raywenderlich Tutorial • Raywenderlich Swift Tutorial • Github Tutorials • Background Tasks
- 58. Thank you