Author : Ishtek
Discussing Architectures on Android Platform.
Before discussing about various approaches towards Mobile Application Architecture
on Android Platform, let us discuss some basic building block on Android Platform.
Various building blocks on Android Platform would be starting from the level from bottom
to top, it is the Linux Kernel along with various drivers (such as display driver,
, camera driver, Flash Memory Driver, IPC or Binder driver, keypad driver, WiFi driver,
Audio driver, power management etc.) then there is a layer on top of Linux Kernel layer,
with various libraries (such as Surface manager, Media Frameworks, SQLite, OpenGL(ES), FreeType,
Webkit, SGL, SSL, libc etc.) and Android runtime with Android specific core libraries along with
Dalvik Virtual machine. On top of this layer there is another layer of Application Framework with
Android Application Managers (such as Activity Manager, Package Manager, Telephony Manager,
Resource Manager, Window Manager, Location Manager, Notification Manager, along Content Providers
and View System etc.). On top of this layer with Managers/Application Frameworks, there is another
layer consists of various inbuilt Applications and user defined/developer's applications to reside.
This top-most layer contains applications such as Home, Contacts, Phone, Browser, SMS, Application
Tools (such as Calculator, Calendar, and many more) etc.
Now let us discuss on various approaches that could be useful while designing/developing applications
on Android Platform.
What would be a good approach to follow while considering various aspects of application architecting
targeted for Android Platform.
Will MVC pattern be useful or any other thick client specific pattern to be considered, while designing
architecture of application on Android Platform.
There are many important NFRs such as Security, Integrity, Privacy etc. mostly concerned with device
and connectivity related aspects, how are these concerns being taken into consideration while designing
appropriate Architecture on Android Platform.
As far as Security aspects for Mobile devices with Android OS, there is a web page with some information
and I think it surely could be a starter/pointer for further studies on Security.
LINK - http://source.android.com/tech/security/
| If interested in commenting related to Android Architecture Discussions
|Name: usingframeworks||Dated: 2013-10-20 17:23:03
What would be acceptable approach while defining Architecture of an application that
would be a client interface for a remote web service,
whether web service is soap based or REST based. Will the Architecture would be able to address relatively most of the NFR/concerns that
would generally come up while designing an Enterprise Application meant for Android Device, or
any other smartphone.
|Name: Ishtek (Author)||Dated: 2013-10-21 21:40:26|
Any Architecture of a system would definitely address most of the Functional as well as non-functional aspects/concerns of a sub system.
Identifying various sub systems, protocols used for communicating and type of data exchanged
as message. Once these aspects are identified, then other concerns would be security, performance, availability as well as salable or not.
I think for deciding on what would be the type of service that is exposed for the smartphone to consume,
whether SOAP or REST, the complexity of the client code would depend on this. Whereas communication protocol can be HTTP/HTTPS irrespective of SOAP or REST based webservice.
This is my 2 cents on this very topic, but you would require many more aspects to consider for defining an appropriate Architecture.
|Name: Girish||Dated: 2013-10-22 21:45:52|
I am looking for some guidance in defining architecture to include Internationalization (i18n)
to the application on Android Platform.
|Name: Ishtek (Author)||Dated: 2013-10-22 21:48:09
How about creating UI layer such as not require to upgrade in case new features are introduced,
rather the UI would remotely download screen from server, by using WebView at the client side?
|Name: Girish||Dated: 2013-10-26 23:29:03
Can you please share your thought on a specific scenario, I am trying to find answers?
How to use OAuth as mechanism to achieve SSO in an application that would be deployed on to an Android Platform.
Any ideas I would always welcome...
|Name: Rani||Dated: 2013-12-31 22:42:32
What is the best way to address concerns relate security while formulating Architecture for an application,
on Android Platform?
Any source code found on any of the page(s) in Techiecommunity.net is associated with following notice:
* TECHIECOMMUNITY.NET MAKES NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY OF
* THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
* TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
* PARTICULAR PURPOSE, OR NON-INFRINGEMENT. TECHIECOMMUNITY.NET SHALL NOT BE LIABLE FOR
* ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING, MODIFYING OR
* DISTRIBUTING THIS SOFTWARE OR ITS DERIVATIVES.
* THIS SOFTWARE IS NOT DESIGNED OR INTENDED FOR USE OR RESALE AS ON-LINE
* CONTROL EQUIPMENT IN HAZARDOUS ENVIRONMENTS REQUIRING FAIL-SAFE
* PERFORMANCE, SUCH AS IN THE OPERATION OF NUCLEAR FACILITIES, AIRCRAFT
* NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, DIRECT LIFE
* SUPPORT MACHINES, OR WEAPONS SYSTEMS, IN WHICH THE FAILURE OF THE
* SOFTWARE COULD LEAD DIRECTLY TO DEATH, PERSONAL INJURY, OR SEVERE
* PHYSICAL OR ENVIRONMENTAL DAMAGE ("HIGH RISK ACTIVITIES"). TECHIECOMMUNITY.NET
* SPECIFICALLY DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR
* HIGH RISK ACTIVITIES.
The content provided in this page is NOT warranted and/or NOT guaranteed by techiecommunity.net .
techiecommunity.net is not liable for any negative consequences that may result/arise from
implementing directly/indirectly any information covered in these pages/articles/tutorials.
For any of the content, if you would like to bring it to notice for removal from this web site,
please write to this web site administrator @ EMAIL-ID (please remove space before and after @),
with appropriate concern and supporting proof(s). After thorough review and if found genuine concern,
we would take appropriate action and remove disputed content from this web site within 24 hours
starting from the time it has brought to techiecommunity.net Administrator notice.
And to provide more relevant ads.