Omar iTech is a modern technology platform providing fast, reliable, and affordable digital services. The product exists so that everyday customers can, in one convenient place:
The audience is the everyday consumer of digital services — customers in Nigeria and comparable markets who are often on mid-range Android devices and patchy connections, and who need a service platform that feels like dependable public infrastructure rather than a startup landing page. The register is trust, speed, and legibility: "this will just work."
This document specifies the current, buildable product: a customer-facing application with a public entry surface, self-service enrollment and returning verification, a browsable catalogue of tech products and digital services, a data-bundle purchase surface, a durable order-management surface, and a support surface — all owned by the application and reachable from one place.
Omar iTech is delivered as a first-party application with custom UI. A single active human role — the Customer — uses the platform end to end. The application owns identity: a customer establishes an account once through self-service enrollment, and returning customers verify themselves before reaching their purchases, orders, and support activity.
Current accepted behavior, by area:
The platform is backed by application services and durable storage so that orders, purchases, and support activity persist and remain bound to the correct customer across sessions.
Narrow exclusions for the current horizon: no administrative, staff, or operator console is specified; no multi-role permission model is specified; no provider-owned or external-only surface is specified; no headless-only delivery is specified. The reusable trading-analysis skill surfaced during planning is not part of this product and is not incorporated.
Delivery ownership. All accepted customer-facing behavior is delivered as first-party custom UI owned by the Omar iTech application. There is no accepted provider-owned surface, no external destination that owns a customer outcome, and no headless-only delivery path. Backend services and storage support the application but do not replace any customer interaction.
Access ownership. The application owns customer identity. Because purchases, orders, and support activity are durable, customer-specific, and must remain bound to the correct participant, identity continuity is indispensable. The Landing, Sign Up, and Login surfaces are reachable without an established session; Data Bundles, Orders, and Support require a verified customer session. Products is browsable without an established session so that prospective customers can see what the platform offers before enrolling.
Current vs. future. Everything specified in Sections 3 through 5 is current. No future-horizon requirements were accepted in the authoritative thread; Section 11 records the boundaries and assumptions that keep the current scope narrow.
Not applicable. No reference directive in this project declares content_source authority, so no source content inventory is rendered.
Each requirement is a distinct story point with its provenance, lifecycle facts, and observable acceptance.
FR-1 — Platform promise and one-place access (explicit) As a Customer, I should be able to reach tech products and services, data bundles, my orders, and support from one convenient place, so that I do not have to move between separate services.
FR-2 — Access tech products and services (explicit) As a Customer, I should be able to browse the technology products and digital services the platform offers, so that I can see what is available and what it costs.
FR-3 — Purchase data bundles (explicit) As a Customer, I should be able to select and purchase an available data bundle, so that I get connectivity quickly and at a price I can see up front.
FR-4 — Manage orders (explicit) As a Customer, I should be able to review and manage my orders and purchases, so that I know what I bought, what it cost, and where it is.
FR-5 — Receive quick support (explicit) As a Customer, I should be able to raise a support request and see its state, so that a problem gets resolved without leaving the platform.
FR-6 — Customer self-service enrollment (required_inference) As a Customer, I should be able to establish my own account before my first protected use, so that my purchases, orders, and support activity are bound to me.
FR-7 — Returning customer verification (required_inference) As a Customer, I should be able to verify myself when I return, so that I can get back to my own purchases, orders, and support activity.
FR-8 — Durable, customer-bound state (required_inference) As a Customer, I should find my purchases, orders, and support activity still there and still mine when I return, so that the platform is dependable rather than ephemeral.
Product context. The Customer is the primary and only active human role on Omar iTech. They are an everyday consumer of digital services — often on a mid-range Android phone over a patchy connection — who needs connectivity, tech products, and services without friction, and who is sensitive to price and to whether a platform can be trusted with their money and their order.
Primary goal. To complete a fast, reliable, affordable transaction and get their support need resolved, with their purchases, orders, and support activity kept in one convenient place.
Distinct accepted responsibilities.
Relevant inputs and decisions. Which product or service they want; which bundle to buy, judged on volume, validity, and price; whether to commit to the purchase; whether an order needs support; what to describe in a support request and whether to reference a specific order.
Interactions with other accepted participants. None. The Customer is the only accepted active human role; there is no counterparty, approver, or agent in the current scope. The platform's backend services and storage support the Customer's work but are not participants.
Observable success. The Customer reaches the catalogue and sees real prices; a bundle purchase is confirmed and appears as an order with a visible status progression; their orders and support requests are still there and still theirs on return; a support request is submitted and shows a state.
What makes this role's work different. The Customer is simultaneously the buyer, the account holder, and the support requester. Their work is a continuous loop of discovery → commitment → tracking → resolution, and every step must be legible at a glance on a small screen: prices in tabular numerals, order status as a route diagram, and support state visible without digging. There is no back-office role in this product, so nothing about the Customer's experience may assume an operator is watching.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!