
Overview
Why it exists
The app
The look: Cuaderno del Valle
The website
- It sells the idea — an editorial, forest-green, Apple-style scrolling page with the Traza fingerprint mark that explains taste-matched discovery, learning a coffee's origin, and buying straight from the grower on fair-trade terms.
- It is the public face of the app's content. Pours, coffees and profiles have real web pages (
/p,/c,/u), so when someone shares a pour it opens as a proper page with correct previews — the share-a-pour loop lands on the web, then an "open in app" deep link hands the visitor to the app. - It captures demand with a beta waitlist and carries the unglamorous essentials a real product needs: privacy, terms, an admin surface, and English/Spanish throughout.
Technologies used
- App: Flutter, Riverpod for state, go_router for navigation, one codebase for iOS, Android and web.
- Backend: Firebase — Auth, Firestore, Storage, Cloud Messaging and Crashlytics, with Cloud Functions (Node) for notifications, aggregate counts and moderation.
- Architecture: a repository seam with interchangeable in-memory and Firestore implementations; hand-written Firestore security rules with their own test suite; 32 test files across the app.
- Website: Next.js (App Router), statically prerendered, with Firebase for the waitlist and public profile pages, bilingual (ES/EN).
- Release: Fastlane with an App Store Connect API key for hands-off TestFlight builds; internal and external beta tracks.
