📄️ Clients
The account is the center for each user, business, developer, etc.
📄️ Account
These accounts are for the end users, not to be misstaken with "Clients" (Accounts). Users can be implemnted two levels, on the Clienet or on the Project, in other words users can be project spesifict or shared across multiple projects.
📄️ Authentication
GO will have a single auth for all the features and apps that are part of it, even though each app will be packdged seperatly the auth is one.
📄️ Launcher
We want to build one app that andles many apps, that means when any app is downloaded City, Transit, or otherwise, it needs to istall the main Go app to handle Slpash, Intro Authentication, etc. We also want each app to have its own app icon in the launcher. This may mean some extra work in the begining but will make the merger of apps much simpler in the future.
📄️ Access
This is the centralized system for handling all access across the entire GO app and sun-apps, including shared trips, lists and more. Access is handled by BackBone.
📄️ Profile
This is the centralized system for handling all access across the entire BackBone ecosystem, from projects, client and user to every part of every endpoint avalible though our Services.
📄️ Trips
Many of the features we are building will inclute "Trips" in City we will eventualy allow a user to plan a Trip, in Transit, in Jar and more. the goal is to centrelize the Trips data into a single feature so it can be used in many ways.
📄️ Bookmark
📄️ Intro
Onboarding is part of the main app but depending on what launcher is used, the user will see diferent text and images on each step.
📄️ logs
Logs
📄️ Onboarding
The goal with backbone CLI is to make setup and other dev tools avalible for developers through the command line, by creating an endpoint or enabling it on each endpoint we are ensuring that any terminal can utilize the CLI functions