ANDROID FOR DEVELOPERS

SERIOUSLY MOBILE PROGRAMMIG
MVC

How long does it take to make a mobile app?

From: Kinvey Backend as a Service

link for pic:http://www.kinvey.com/blog/images/2013/01/how-long-does-it-take-to-build-an-app-kinvey-1500x834.png

This is a very well described infographic about how is really development of an application for mobile, is not so easy and kind, If you want really make it good.

Usually the way for development an application is using the MVC paradigm, as is possible to see on the link, is not only an architecture, is a point of view to create the structure of our applications, WHAT THAT MEANS? it means there are 3 modules for creating an applications:

for the purpose of explain clearly we are going to suppose that our application is simple we just need to create a view with a button that shows the time on a label. 

MODEL:

Defines what, when, where is gonna do the application, usually is represented as a lifecycle of each requirement. WHAT? yes on our application is simple is like this: 

VIEW:

it can be defined as the layout (in android xml) usually represents the Human-android interaction for example buttons, list, images, feedbacks, sounds, etc. On android studio it can be see as: 

CONTROLLER:

The controller defines the behavior of each component of view, for example if you define a button on your layout/view when user clicks the buttons it's gonna do nothing, then the behavior for the event triggered when user clicks is necessary to be programmed for android is used JAVA, this is an example of code in java for button clicked event handling:

Then as my experience programming can advise me we can have 2 different approach for develop apps,  in both cases we have almost clear and is evident what we need the app have to do.

This is referred to the application well made development stack, is something like this:

TOP-DOWN: 

This approach is usually used when is clear the graphic propose, it means we have absolutely clear how's gonna look the app but we don't know if is feasible or how can be do it so the first step is develop all the layouts with empty controllers and then depending of desired behavior (model) we can later define how to programming them, for example if some data for a list is get it from web service or is local, or if is fixed.

BOTTOM-UP: 

This approach is necessary when we have clear how to do the app but not exactly how is gonna look, because sometimes the UX-designers did not define yet the user interface at the beginning of development so we can establish a definition for data objects, data helpers, services connectors, parsers, and all what we need to have the data when layouts are going to be ready to develop.