HoyPromete
A product vision started in 2016 to connect nearby places, events, and promotions, rebuilt as a modular platform with an honest boundary between design, implementation, and evolution.
Summary
HoyPromete is a long-running owned product exploring how people discover nearby places, events, and promotions. The idea began in 2016 and evolved from broad research and prototypes into a modern technical rebuild started in 2024.
The case demonstrates product thinking, extensive visual coverage, and an implemented foundation for identity, shared contracts, asynchronous events, and transactional email. The page clearly separates designed vision, working software, and the next stage.
01Context
The original idea emerged in 2016 from observing that discovering what to do nearby depended on too many disconnected sources. HoyPromete became a sustained exploration of context, intent, and local life.
HoyPromete did not begin as a directory of places. It began as a question: how can intent, context, and local life become one useful experience?
- Relate places, events, and promotions without reducing the product to a generic directory.
- Support search, filters, detail, saves, activity, and profiles through one shared grammar.
- Build the technical base in stages without presenting the complete vision as delivered software.
02Problem
Local discovery is fragmented across social platforms, search, recommendations, and individual sites. The challenge was not gathering listings; it was designing a useful decision that connected context, relevance, trust, and continuity across surfaces.
03Solution
Design the complete discovery system first, then rebuild it by capability: identity, contracts, shared UI, asynchronous events, and communication. This sequence preserves the vision without forcing a monolithic implementation.
identity command
-> Firebase Auth
domain event
-> Pub/Sub -> Cloud Functions
notification
-> Maizzle -> AWS SES04Execution
The modern rebuild uses Next.js and React in a monorepo, Firebase for identity, Pub/Sub and Functions for events, and Maizzle with AWS SES for email. Implemented flows cover access, registration, recovery, and activation; discovery, mobile, and broader profiles remain designed capabilities in evolution.
Architecture and decisions
01. Discovery as a decision
Places, events, and promotions share context and intent; the product is organized around the user decision rather than a content taxonomy.
02. Vision before isolated screens
Sketch documents complete journeys and reusable components to validate the system before every module is implemented.
03. Capability-driven rebuild
The monorepo separates application, authentication, functions, email, and shared packages for incremental evolution.
04. Decoupled events and communication
Pub/Sub, Cloud Functions, and transactional email prepare asynchronous flows without coupling them to the interface.
Evidence and records
A visual reading of the product thesis, the fragmentation problem, and the discovery system envisioned since 2016.
From the Sketch document to an implementable strategy: journeys, components, states, and mobile-first decisions.
The working foundation for identity, contracts, events, and email, separated from capabilities still in evolution.