| Feature Name | Plan-At Client |
| Area | Frontend |
| Related Features | Flutter |
| Requirement Specs | |
| Document Location | https://github.com/Plan-At/PlanAt-Client-Flutter |
| Spec Status | Draft |
| Role | Name |
|---|---|
| Manager | Chad Magendanz |
| Developer |
| Author | Date | Version | Comment |
|---|---|---|---|
| - | 04/19/2022 | Initial Draft | Created this page |
Alternative frontend for Plan-At using Flutter. Since our backend "API First" and the whole project is intended for multiple variation of frontend/client
Oringinally our client is planned using ReactJS, but its somewhat hard to use, no one likes it, and we have little or no progress, therefore we need some ground-breaking changes, by develop two version of client once, for minimize the risk
Sections of the project:
- Framework Selection: For the framework, we wanted a framework that's easy to use and shorten developemnt cycle, and runs on all platform with single codebase. So Flutter is the best choose, and set up an enviornment and repo to began development.
- Quick Demo: We want to show the superiority of Flutter by its really easy to use.
- Project Breakdown: Our next step was to break down our project into multiple packages, and the priority is provide some mock data for the frontend team.
While resizing the text and image isn't hard, but is where to place elements: For example the navigation rail, available to put on the left side in landscape mode, but in mobile must place on the bottom of screen