Components

The Component libarray is a database filled with flutter widgets and details documentation on what it is good for, Colibri will not only understand the flutter code but its documentation, the goal is to choose the right widget without the need for much or any code modification, rather colibri should focus on use intent and connetion with the corect action.

Task Chat Branch API

note

These details are only updated with each release, for more acurate updates and keeping track of progress, see the task in GitHub.

---

Feature Details

Team

Owner	Lead
Mendy	Esti

Status

Doc Status	Product Status	Last Update	Version	Release	Phase
In Progress	Up Next	04.03.2024	0.01	Internal	Alpha

---

Description

Colibri should build a flow plan that matches the action plan, then find the componets that best fill that plan. Colibri should have the ability to modify code to ensure all widgets make a matching theme so controle the style file that all widgets must adhear to.

Reminders

Links & Resources

Research

Research

note

the research listed here is spesifict to the Chat feature, for research related to the general Colibri 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 Details

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

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.

• Actions

  Create an api to allow apps to add thier own actions in the place of the voice and live actions

• Modes

  Allow the user to chnage to diferent modes or create thier own modes

• Apps

• Actions

• Live

• Groups

• Threads

• Chat Suggestions

• Post

• Access

  If the account type is not "indiviual" the account will not have an auth method and thefore will reqesre access. This will be a sub-collection within the account document that will hold the account, group, etc IDs of anyone who has access to this account.

• @

  In any chat the user can use the @ symbole to mention a user by name, username, number or email, they can mention an app, mode and more

• /

Data

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.

Messages

- Message
- - Message 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

Intelegence

    - names
    - - name 1
    - - - type (legal, nicname, madename, etc)
    - - - name
    - - - laguadge
    - - - created (date)
    - - - varified (true, false)
    - - - varified source (api id)

Identification

    - id
    - - id 1
    - - - type (licence, passport, health card, etc)
    - - - issuer (US gov)
    - - - id number
    - - - status: verified
    - - - issued (date)
    - - - experation (date)
    - - - Verify provider: (api id)
    - - - Verify date: log id
    - - - image
    - - - id_proof`

Condissions

    - Sessions
    - - Section #1
    - - - auth type (OTP, Google, Apple, Normal)
    - - - device_type (Android, IOS, Web)
    - - - device_token
    - - - location
    - - - activated (date)
    - - - status (active, inactive)
    - - - inactive (date)

Knowladge

Envierment

• location
• mood
• tone

Preferences

- prefrences
- - communication
    - - - method (push, email, text)
    - - - default (true, false)
    - - - allow (true, false)
    - - - block (true, false)
    - - - level (all, update, security, system)
    - - - channels (id, id, id)
    - - privacy
    - - - allow (true, false)
    - - - block (true, false)
    - - - allow user data collection (true, false)
    - - - allow user data share (true, false)
    - - - allow user data anonymize (true, false)
    - - - allow user data deletion (true, false)