To create a "boiler plate" project to be used as the bases for a larger project later. That is; to create a fairly generic app that implements functions that can then be re purposed for other uses. Consider "CRUD" type operations that appear in pretty much every app at some point and most programmers have boilerplate CRUD code they can just re-purpose. This app aims to create a similar backend - front end communications app that can then be re-purposed. You may even have something you already use for most of what this project is asking for.
The app will have 4 capabilities: 1) Authentication. Sign in/sign out. If you have no account sign up with some details entered in a form (e.g. Email address, name, address, post/zip code) 2) View some data as a list. for this app I have decide on a forum thread list with five columns - subject, poster name, date, number of replies so far, number of views. 3) A chat app. For this app the chats will be the replies to the forum threads. Click the forum thread you're interested in then join the chat. Here Authentication comes in - you cannot chat unless you are authenticated by 1) above. 4) Notifications. Notify the user of stuff - for our boiler plate app notify the user that their thread has received replies.
Data and Storage. The app will be a client server model with local data storage for a limited set of records. If connected to the internet data for the list and chats will be fetched in real time and received as JSON. A limited set of data will be stored locally. In this case the last 30 days with older items removed locally. Scrolling back through chats and forum items beyond 30 days will require an internet connection. Server will provide pagination.
Data Requests Data CRUD requests will be made to the server with the authentication token (if any) attached. https to be used. A new token may be passed back in a session, but it should be assumed that the same token will be used throughout under normal conditions. This will probably be a simple integer or alpha numeric token. Obviously token errors will need to be handled smoothly (error message -> re login option - return to the chat or list page smoothly)
Synchronization. Chats entered offline will be held until online then synchronized with the server.
Reasoning: These four things make up the heart of many apps; lists of stuff such as products, members, messages; some way to share or communicate; authentication and members only type sections; ways to send messages to users/members.
Code re-useability Time will be spent ultimately getting these four functions "right" before the underlying code can then be re-purposed for other sections of the app. Thus classes and code re-useablity needs to be considered in the design.
Technology stack The front end should be developed in Flutter/Dart for a cross platform audience - web, Android, iPhone. The server delivers JSON and response to authentication tokens with either data or an authentication error. What technology is driving the data delivery should not be of your concern.
The project will not use Firebase. It should be server agnostic.
Ideally the MS visual studio code should be used for editing.
All code to be provided (this is a code creation project) with no licensing issues for use. If using existing boiler plate in your possession a non-exclusive re-use right should be given.
Clearly this is the start of something larger ....
