{"id":6272,"date":"2018-06-22T20:15:13","date_gmt":"2018-06-22T14:45:13","guid":{"rendered":"https:\/\/www.konstantinfo.com\/blog\/?p=6272"},"modified":"2018-06-22T20:15:32","modified_gmt":"2018-06-22T14:45:32","slug":"android-app-architecture-to-streamline-the-app-development-process","status":"publish","type":"post","link":"https:\/\/www.konstantinfo.com\/konstant-blog\/android-app-architecture-to-streamline-the-app-development-process\/","title":{"rendered":"Tutorial- Why and How to implement Android App Architecture to Streamline the Overall App Development Process"},"content":{"rendered":"

Pinal Jakhar<\/strong>– an Android developer at the firm, takes an hour long session on Android app architecture and how its implementation can help overcome the most common challenges developers face. The engaging and resourceful session earned her much regard followed by a token of appreciation. Here is a layout of the session:<\/em><\/p><\/blockquote>\n

\"android<\/p>\n

A report <\/a>(pdf) published at the University of Luxembourg in 2015, found that over 60% of an Android apps\u2019 code was contributed by common libraries. Most of such libraries include ads and analytics from Google, social plugins, common widgets, among others. That means more than half the resources (of which mobile devices are highly constrained) is drained by processes irrelevant to core business logic.\u00a0 And given that we still use most of those libraries, it can be safely assumed the situation hasn\u2019t changed much since 2015.<\/p>\n

No, libraries themselves aren\u2019t the problem. They are extremely resourceful and there is no way we can build apps without them. But the point is if more than half the code and device resources are channeled to common housekeeping tasks, it becomes essential that the code we do write for the core business logic brings the highest level of efficiency.\u00a0 And that is what this post is about- the problems in Android app development and the how we can streamline the process by effective implementation of latest libraries to boost quality while managing deadlines.<\/p>\n

\"android-trainning-session\"<\/p>\n

The current scenario<\/h2>\n

To understand the better way to building an app, we first have to outline what actually constitutes building an app. In its most rudimentary form, the process involves these broad steps:<\/p>\n

Routine repetitive tasks <\/strong><\/p>\n

Building applications always start with the same basic set of steps- creating packages, managing versions and elements, and those dozens of other tasks that have to be repeated like clockwork for each application.<\/p>\n

Network communication <\/strong><\/p>\n

The next in line is network management. Because mobile devices often work in patchy network reception, apps need to be highly resilient to server timeouts, lost response, or any other kind of network error for that matter.<\/p>\n

Data storage <\/strong><\/p>\n

Applications essentially run on data and while there is always the main database at the backend, the tricky part is to decide how data flows through different processes and which data source to use for each type of user action. Eventually, it all boils down to the speed of local storage vs accuracy of fetching it from the server.<\/p>\n

Data display <\/strong><\/p>\n

This relates to the UI aspect of the application that users actually see. While the primary task of UI components is to display data, it also has to change its own behavior depending on the data being displayed.<\/p>\n

Data manipulation <\/strong><\/p>\n

This is where the core business logic is applied and has to take into account all different components.<\/p>\n

Architecture<\/strong><\/p>\n

Both of the above operations are implemented in specific architectures of which two of the most popular are MVP and MVVM:<\/p>\n