Details
BackBone is a platform for selling micro services (AKA APIs and Endpoints), Services are these products packged in micro services. While they each have thier own servers and backend, here we keep a list of them all, who is the publisher, pricing, and all other details, you can think of this as a marketplace.
Task Chat Branch API- Status & Details
- Research
- User Focused
- Features & Functions
- Data
Status
| Doc Status | Product Status | Last Update | Version | Release | Phase |
|---|---|---|---|---|---|
| In Progress | Up Next | 04.03.2024 | 0.01 | Internal | Alpha |
Team
| Product Owner | Lead | Member #1 | Member #2 |
|---|---|---|---|
| Mendy | Esti | Nir | - |
These details are only updated with each release, for more acurate updates and keeping track of progress, see the task in GitHub.
Description
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 - How do we get data from arenas to form the arena layout and map the devices?
Answer - In our research we found many [API]s that give us much information but they are all very limited and expensive.
We
Conclusion - How do we get data from arenas to form the arena layout and map the devices?
Sources
- [test]
Business
User Stories
Persona One
Update Coming Soon
As a busy user I don’t want to watch but rather listen to a podcast, however, when I hear a voice I don’t recognize, I want to take a glance at my phone to see a name and/or photo of who is talking or maybe ask the built-in “AI/assistant”.
Flows
Personas
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.
-
Publish
To publish a service the user can use the publish prompt or button from the project, this will generate a service document and set the ststus to "request".
-
Ratings & Reviews
Allow anyone useing a services to leave a review.
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
- Services
- - Service 1
- - - type
- - - created (date)
- - - timezone
- - - status
- - - version
- - - latest release
Usage
- active users
- active clients
- usage by version
Revenue
Releases
- name
- version
- by
- size