XamarinSubodh N PushpakDay TwoIND 14-16 Dec.AgendaDay 1Introduction to Xamarin / set up Demos: Xamarin development approachesDay 2Introduction to AndroidDemos: Android app with layouts, list view, adapters, navigation Day 3Advanced Android conceptsDemos: Advanced features like Fragments, GPS, Maps etc.IND 14-16 Dec.AgendaAndroid FundamentalsMVC PatternActivityActivity LifecycleViewNavigation among ActivitiesIntentsHanding rotationsList view / adaptersLayouts / controls
IND 14-16 Dec.Android FundamentalsThe MVC Pattern MVC in AndroidActivities and LifecyclesFragments and lifecycleThe Application UI - The UI Control SystemDesigner BasicsResources and LayoutsCoordinate SystemApplication LifecycleFonts & ImagesIND 14-16 Dec.The ModelThemodelrepresents the data. It responds to requests for information about its state (usually from the view), and responds to instructions to change state (usually from the controller).Business objects, services, data access etcAmodelrepresents the state of a particular aspect of the application. Frequently, a model maps to a database table with the entries in the table representing the state of the applicationIND 14-16 Dec.ControllersAcontrollerhandles interactions and updates the model to reflect a change in state of the application, and then passes information to the view.Direct all the action of a requestMake calls to models to gather dataController classes are invoked in response to an incoming URL request. A controller class is where you write the code that handles the incoming parameters, retrieves data from a database, and ultimately decides what type of response to send back to the browser. View templates can then be used from a controller to generate and format an HTML response to the browser.IND 14-16 Dec.ViewAview accepts necessary information from the controller and renders a user interface to display that.Responsible for displaying data.May interact with model but shouldnt make decisions over what entities to display, shouldnt make CRUD actions etc.
IND 14-16 Dec.Android - ActivitiesActivities are a fundamental building block of Android applicationsAndroid applications can be launched via any registered activity within an application.Activity LifecycleActive or RunningPausedStopped/Back groundedRestartedIND 14-16 Dec.Android - ActivitiesAn Activity is a special Android class that corresponds to a single application screen, and is responsible for drawing and powering the user interface. When Android creates an applications first Activity, it loads the entire applicationIND 14-16 Dec.Android - Activities
IND 14-16 Dec.Android ManifestThe role of theAndroid Manifestis to keep track of an applications contents, properties, and permissions and disclose them to the Android operating system.
IND 14-16 Dec.Android Activity Lifecycle
Saving and retrieving the instance state in the Bundle:
OnSaveInstanceState OnRestoreInstanceState IND 14-16 Dec.IntentAndroid is designed around the principle of least privilege- applications have access to only the Blocks they require to work, and limited access to the Blocks that make up the operating system or other applications. In order to communicate, Application Blocks send asynchronous messages calledIntentsback and forth. Intents contain information about the receiving Block and sometimes some data. An Intent sent from one App Component triggers something to happen in another App Component, binding the two App Components and allowing them to communicate.IND 14-16 Dec.List View / AdaptersIND 14-16 Dec.DemosBuilding the First Android applicationUnderstanding the solution structureCreating a ViewUnderstanding Activities and eventsUnderstanding NavigationLayoutsResourcesList view / adpaters
IND 14-16 Dec.Questions & AnswersIND 14-16 Dec.