📄️ 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.
📄️ 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.
📄️ 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
📄️ Home
Here the user can start a Journey, see exsisting ones, see tickets and passes they have purchaced and start a new serch/journey.
📄️ Locator
Locator is a group of features to allows a user to locate any item (e.g. washrooms, benches, drinking water, etc) on a map not previusly avalible on other map products.
📄️ Drop
📄️ Details
Jar is a ride sharing app, enicialy meant for finding drivers, passnerder or rides to go from city to city. At a later stage this will be merged with the GO app to allow a lot more features like renting a car, planning a trip and more transport and mapping features.
📄️ City
GO City is a fun simple app to learn fun facts about random cities around the world.
📄️ Jar
Jar is a ride sharing app, enicialy meant for finding drivers, passnerder or rides to go from city to city. At a later stage this will be merged with the GO app to allow a lot more features like renting a car, planning a trip and more transport and mapping features.
📄️ Clients
The account is the center for each user, business, developer, etc.
📄️ 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.
📄️ 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.
📄️ Quiz
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.
📄️ Transit
<Button
📄️ 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.
📄️ Checkout
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.
📄️ Cities
The "Cities" view is where we show a virtical carosel of vities, wish swipe showing a new random city.
📄️ Services
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.
📄️ City Details
Add a short description
📄️ Billing
📄️ Bookmark
📄️ buffet
📄️ CLI
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
📄️ Driver
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
📄️ logs
Logs
📄️ Passes & Tickets
📄️ passenger
Passenger
📄️ search
📄️ Real-Time Asset Tracking and Visibility
- Description: Provides instant visibility into the location, status, and usage of assets using technologies like RFID, barcodes, QR codes, or IoT sensors.