Apps
Apps are a compelation of actions and components, each app is a file detailing each screen, what component and actions to use from ther respective library. it functions exactly the same way as generated flows except we skip the generation step and rely only on the developers instructions.
Task Chat Branch API- Status & Details
- Research
- User Focused
- Features & Functions
- Data
Team
| Owner | Lead |
|---|---|
| Mendy | - |
Status
| Doc Status | Product Status | Last Update | Version | Release | Phase |
|---|---|---|---|---|---|
| In Progress | Up Next | 04.03.2024 | 0.01 | Internal | Alpha |
These details are only updated with each release, for more acurate updates and keeping track of progress, see the task in GitHub.
Description
Apps are a temporary measure, while we work on perfecting the Actions Flow and UX Flow, we will relly on developers to build the user experiance. It can also be used to establish an independet brand.
Reminders
Links & Resources
Research
the research listed here is spesifict to the User (Account) feature, for research related to the general BackBone development see the Research document.
Technical
Question - Answer -
Conclusion -
Sources
- [test]
Business
Features
Below is a list of features that will be utilized in order to deliver the best account features and functionalities. The details bellow are not comprehensive feature details but rather, describe how the features will be utilized within the account, for further details, please see the individual feature documentation.
On the document we want to keep all the important data, the first fetch and fast to access, all secondary data should be stored on a subcollection and fetch sepratly (if this is cost sfective)
User Accounts should be a top level collection, each account will generate a new document within the "Accounts" collection.
Account
- Account
- - Acount 1
- - - type (offer a fea default options that the client can configure as well as custome options or offer numbered types and allow te client to give each type a title, this will enable the client to offer difrent feature or access levels based on account types)
- - - email
- - - number
- - - legal name (if connected wit a / our identity API this will allow for name/identity varification, useful for saftly and fintech and fraud protection)
- - - age (also opcinaly connect with identity api for varification)
- - - dob (also opcinaly connect with identity api for varification)
- - - varified (true, false)
- - - created (date)
- - - timezone
- - - langages
- - - contact detail