Jump to content
Toggle sidebar
Logos
Search
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information
Editing
Status/Requirements
(section)
Page
Discussion
English
Read
Edit
View history
More
Read
Edit
View history
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== 2. Overall Description == <span id="product-perspective"></span> === 2.1 Product Perspective === Status is a SuperApp, a mini operating system that integrates with the Logos Microkernel ecosystem. Its primary role is to display UI modules and allow users to interact with them, similar to how an operating system shell provides an environment for applications. The framework enables functionality similar to: * Secure messaging apps (Signal/Telegram) through messaging modules * Financial services apps (Cash App/Venmo) through financial modules * Super apps (WeChat/LINE) through its modular architecture While Status operates independently, it relies on: * Logos Microkernel for core functionality and module coordination * PDMS for data management * Modman for module package management * Individual modules for specific features and services <span id="product-functions"></span> === 2.2 Product Functions === Major framework functions include: # Core Framework Services #* Module lifecycle management through Modman module (installation, updates, removal) #* Window management and UI coordination #* Account and authentication management #* System-wide notification handling #* Inter-module communication facilitation, through the Microkernel # UI Module Support Services #* Shared UI component library for consistent module display #* UI layout and window management coordination #* Module display state management #* UI event distribution to modules Note: Core module services (isolation, sandboxing, lifecycle management, and inter-module communication) are provided by the Logos Microkernel and its core microservice modules. # User Experience Services #* Module discovery interface #* Global search and navigation #* System-wide settings management #* Cross-module data sharing (when permitted) Note: Specific features like messaging, cryptocurrency transactions, and DApp interactions are provided through modules. Some core modules to Status (like DApp Browser, Account Management) are bundled with Status, while others can be added by users. <span id="user-classes-and-characteristics"></span> === 2.3 User Classes and Characteristics === Primary user classes include: # Regular Users #* Require basic messaging and financial features #* May have limited technical knowledge #* Focus on ease of use and security # Crypto Enthusiasts #* Actively use cryptocurrency features #* Interact with DApps #* Higher technical proficiency # Developers #* Create and deploy modules #* Integrate services with the platform #* Require technical documentation and APIs # Business Users #* Use platform for commercial purposes #* Require integration with business services #* Focus on reliability and support <span id="operating-environment"></span> === 2.4 Operating Environment === The application MUST run on: * Desktop: Linux, Windows, macOS * Mobile: Android, iOS Technical requirements: * Written in Nim/C++ using Qt framework * Integrates Logos Microkernel as a library * Supports WebAssembly for module execution * Requires internet connectivity * Supports various screen sizes and orientations <span id="design-and-implementation-constraints"></span> === 2.5 Design and Implementation Constraints === * iOS restrictions on dynamic code execution require special handling * Must comply with various app store policies * Security requirements for handling financial transactions * Privacy regulations compliance (GDPR, CCPA, etc.) * Module isolation and sandboxing requirements * Cross-platform compatibility constraints <span id="user-documentation"></span> === 2.6 User Documentation === The following documentation MUST be provided: * User manual and quick start guide * Module development documentation * Security and privacy guidelines * API documentation * Troubleshooting guide <span id="assumptions-and-dependencies"></span> === 2.7 Assumptions and Dependencies === Assumptions: * Users have basic familiarity with mobile/desktop applications * Devices meet minimum hardware requirements * Internet connectivity is generally available Dependencies: * Logos Microkernel * Qt framework * WebAssembly runtime * Blockchain networks * PDMS implementation * Waku module <span id="external-interface-requirements"></span>
Summary:
Please note that all contributions to Logos may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Logos:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)