Mobile‐frontend development plan - muhamed-hassan/safe_planet GitHub Wiki

Training:

Mobile‐frontend development consists of Java as a programming language with Android as a development framework.

Required machine for development purposes:

Desktop computer (Windows OS based) with 16 G RAM, i7 CPU and 250 G SSD

Roles:

  • Java architect [Mobile-frontend]

  • JD of a Senior Java developer [Mobile-frontend].

  • JD of a Junior Java developer [Mobile-frontend].

Necessary tools in local environment

Application packaging format: .apk

It's nice to have a look on code review.

Notes:

  • Reuse the built-in functionality within the programming language and the development framework, then if there is no such kind of built-in functionality, use a library attached to the developed app as an external dependency.

  • Too much unnecessary code and libraries affects the app stability.

    • app is an up and running process at the OS level.

  • Theory is good to be reused wisely, however during development always follow the single thread model and know how to control it upon need.

Git repositories access control:

Java architect [Mobile-frontend]:

  • Have full access to everything for auditing purposes and measuring the variance with the plan upon need

  • Merge feature-branch to master-branch as a 2nd approver

(Junior | Senior) Java developers [Mobile-frontend]:

  • Access to mobile-frontend component made of Java with Android SDK

  • Access to planned wireframes and other resources like used images in mobile-frontend upon completion so the frontend can be constructed effectively

Deployment:

  • Deployment is manual during the development on the local machine to a physical device.

  • You have to deploy the versioned .apk over the physical devices.

Examples:

500238753-637242c7-d304-4ff7-9d28-ffc16be84454