Build an android app skeleton - 2

I need an android app skeleton built using Java for a REST client. By skeleton, I mean structural base for a project. I am experienced with PHP so a good skeleton example I can give is [login to view URL] It has a setup for various features like (I will mark their requirement): - Templating (needed) - Firewall (preferred) - Translations - Routing (needed) - Profiler (preferred) - Debugger (needed) - Logging (needed) - Forms (needed) - Validators (needed) - Caching (needed) - Testing (needed) This skeleton will be used to build an API client in future. So, all development should be done with this in mind. This project will act as a POC or a prototype for that purpose. On top of the skeleton, I need one functionality property implemented. i.e. Authenticating with an API Server and showing a welcome screen. To demonstrate the skeleton within the login mechanism and the welcome, I suggest the following: - Templating (needed) - A layout template for the app - A screen layout for login page and welcome page - A component layout for login form on the login page - Firewall (preferred) - The welcome screen cannot be accessed without being logged in - Translations (skip) - Routing (skip, I don't think native apps can have routes, please correct me if I am wrong) - Profiler (preferred) - While both login and welcome screen is loaded, some profiler report should be saved in the device and/or shown in the client - Debugger (needed) - While both login and welcome screen is loaded, some debug report should be saved device and/or shown in the browser - Logging (needed) - During the processing of the login, the logs should be saved on the device - Forms (needed) - The login form will be loaded using this (It may be natively supported by language) - Validators (needed) - The login form should be validated (It may be natively supported by language) - Caching (needed) - The login and welcome screens will be cached and saved in the device - Testing (needed) - The functionality of the login mechanism should be tested. Design: The design is not important at this stage. The most basic design will work. But it has to be clean and easily extendable and customizable. Framework: I don't want to use any full-featured framework until there is a very good reason for it, so I am open for discussion. But I do require a framework that is suitable for an API client. For example, if the project was for API Server (which it's not), it would be a framework built around MVC Pattern, Repository pattern, Facade, Singleton etc.(Just an example, you don't need to know them, just knowing what I am referring to will suffice) After the prototype is approved, there will be further work on the project. On your bid, please - Include the technologies you are going to use and why? - Details you need before you can start the work. (This will represent your expertise) - Questions you have about the project. - ‎The framework and design patterns you will use. Deliverables: - Fully documented structured code - Fully documented build instructions - Instructions to configure the project - Instructions to launch the prototype Budget: For a skeleton, I think $30-$50 is fair. There must be many open source projects (like the one I linked above) and it just may need to be customized for my requirement or for an API Client. But I am open to paying a good price for good quality work.