Android Plug-In Architecture

PLUG-IN ARCHITECTURE Introduction We need to develop the application in different phases as part of agile/lean methodologies. To develop highly scalable/extendable application, it should follow the best practices of Plug-In architecture. In the first phase of the application we should support the below features: Backend Services: RESTful Web Services using Spring User Registration and Authentication User Management and Privileges Core Application: Plug-In Architecture User Registration and Authentication Data Encryption Multi Language Support User Management and Privileges Analytics Application Release Management Sample Plug-Ins: Contacts Manager Plug-In WhatsApp File Sharing Plug-In In the above features all are non-functional requirements and should be re-usable in any application. So we should make sure that the core application is developed to reuse/extension in mind. So as part of this first phase we highly required excellent architectural design for scaling / enhancing the future requirements/changes in the next phases of the application. Robust design, Coding Best Practices, Error Handling, Performance Optimization and Layout Design for small screens to Big Screens are expected by default from the developers. When copying the code from others make sure that we don’t face any legal issues in future. For more details please go through the attached document. According to current requirements we are expecting 6 to 8 phases of development. Based on the first phase deliveries we will proceed with next phases of the application.