38 lines
2.3 KiB
Markdown
38 lines
2.3 KiB
Markdown
# Product
|
|
|
|
## Register
|
|
|
|
product
|
|
|
|
## Users
|
|
|
|
Customer workers and business owners in Ethiopia. Primary users include accountants, finance staff, managers, and employees who need to scan, send, and reconcile invoices from a mobile device. They work on the go, often switching between physical paperwork and the app.
|
|
|
|
## Product Purpose
|
|
|
|
Yaltopia Tickets is a mobile invoice companion that replaces paper-based invoicing workflows with a scan-to-reconcile pipeline. Users scan paper invoices or receipts with their camera, the app extracts the data, and they can create, send, track, and reconcile invoices and payment requests — all from one device. Success means a business can go from a paper receipt to a reconciled invoice without touching a desktop.
|
|
|
|
## Brand Personality
|
|
|
|
**Efficient, trustworthy, modern.**
|
|
|
|
The tone is professional but not corporate — clear, direct, and confident. Every interaction communicates reliability: data is handled precisely, nothing gets lost. The app should feel like a capable assistant, not another chore.
|
|
|
|
## Anti-references
|
|
|
|
- **Not corporate**: No heavy ERP aesthetics, no navy-and-gray enterprise sterility.
|
|
- **Not cartoonish**: No playful mascots, gamified elements, or toy-like illustrations.
|
|
- **Not generic**: No template-looking screens that could belong to any app.
|
|
- **Not cluttered**: Information-dense when needed, but never overwhelming. Every screen has a clear focal point.
|
|
|
|
## Design Principles
|
|
|
|
1. **Trust through clarity.** Financial data demands precision. Every label, number, and status must be unambiguous. Users should never wonder "did that go through?"
|
|
2. **Efficiency first.** The primary flow is scan → extract → reconcile. Every screen should shave seconds off that pipeline, not add steps. Quick actions, minimal taps.
|
|
3. **Modern without trendiness.** Clean, contemporary, native-feeling iOS/Android UI. No glassmorphism, no gradient text, no decorative flourishes that age poorly.
|
|
4. **Thumb-first mobile.** Designed for one-handed use on a phone. Primary actions within thumb reach, secondary actions tucked away. Forms are compact and scannable.
|
|
|
|
## Accessibility & Inclusion
|
|
|
|
Standard accessibility best practices: sufficient contrast, readable font sizes, touch targets of adequate size. No formal WCAG target, but body text must remain legible in direct sunlight (a real use case for on-the-go workers).
|