This is the planning synthesis that shaped v1. It is not a live market report. Revalidate competitors, pricing, reviews, and commercial assumptions before productization.
These are research references only. QuickCrate does not use their runtime services, code, logos, screenshots, copy, or product photography.
The common quick-commerce journey is:
- Establish delivery address/ETA.
- Offer search, category discovery, and promotional shelves.
- Let shoppers inspect variants and explicitly adjust quantities.
- Keep a persistent cart visible throughout discovery.
- Explain item pricing, savings, fees, threshold, and total before payment.
- Select address/payment and submit once.
- Recover clearly from ambiguous/failed payment.
- Make the resulting order visible with stable purchase details.
QuickCrate adopts this recognizable sequence so a reviewer understands it immediately.
The planning review prioritized recurring user-friction themes rather than growth mechanics:
- Silent cart substitutions, removals, or quantity changes.
- Fees revealed only at the last step.
- A failed payment that loses cart/address/payment context.
- Duplicate orders after rapid taps or retry.
- Order history that changes when the live catalog changes.
- Remote artwork/loading that makes an offline demo look broken.
- Ads, coupons, loyalty, and recommendation noise obscuring the core job.
These became implementation invariants: explicit events, full pre-payment math, FailOnce before persistence, attempt-ID idempotency, immutable snapshots, and local resources.
QuickCrate is not trying to beat a production delivery service on assortment or logistics. Its wedge is a trustworthy, inspectable, fully offline reference journey:
- Every important state can be demonstrated on demand.
- Failure is a first-class path, not a hidden toast.
- Persistence and price math are visible and testable.
- The app can be evaluated without signup, credentials, services, or internet.
- The same Compose Multiplatform module owns UI through persistence.
The Morphing Crate Bar was chosen because it is visible within seconds, belongs directly to the golden path, communicates persistent state, and can remain accessible/reduced-motion-safe. It differentiates the demo without adding a separate novelty feature.
- Target/build platform for v1: Android.
- Reason: quick commerce is naturally mobile, the crate interaction benefits from touch/native behavior, and Android allows the CMP application boundary to be demonstrated credibly.
- Long-term platform/product direction remains a decision gate in
ROADMAP.md.
Keep: delivery context, discovery/search, variants, explicit quantity, persistent crate, full pricing, address/payment choice, recoverable failure, order visibility, and profile/session persistence.
Cut: backend logistics, live inventory, multiple stores/accounts, tracking, support/refunds, notifications, maps, coupons/loyalty, ads/recommendations, pagination, analytics, and real payment/auth.
Repeat the competitive/market/name review before adding a backend, monetization, store submission, production branding, or real user/payment data. Record dated sources and owner decisions in a new research section rather than rewriting this v1 rationale invisibly.