Astronar
A guide to what’s happening in London, organised by date and category and ranked by the people using it.
Astronar turns a fragmented question, ‘What is worth doing in London?’, into a community-ranked path from discovery to registration.
The situation.
Astronar did not begin with a roadmap. Fatema asked on X whether someone could build ‘Product Hunt for events’, and I began testing the idea. The initial build quickly exposed a broader problem: finding something worth doing in London is fragmented across organisers, newsletters, social feeds, and ticketing sites.
That thought became a broader event-discovery product. Astronar organises events by date and category, lets people discuss and vote, surfaces an Event of the Day, and then sends visitors to the original organiser to register.
What I did.
I moved directly from the public prompt into building. As the idea expanded, I set the independent product direction, curation model, interface design, and engineering through W15I.
I treated ranking, comments, and outbound registration as product boundaries. Astronar can help establish relevance and shared context, while the originating organiser remains the source for the actual event and registration.
See Astronar in action.
The first recording walks through the live discovery and event-detail flow. The second shows Event of the Day, Astronar's live retrospective vote for the best event from the previous London day.
From discovery to event details
A walkthrough of Astronar’s main flow: browsing ranked London events, opening an event, joining the conversation, voting, saving it, and following the organiser’s registration link.
Video: Waseef Mohammad KhanEvent of the Day
A walkthrough of the live feature, showing the retrospective daily ballot, eligible events, and the community winner reveal after voting closes.
Video: Waseef Mohammad KhanHow the work unfolded.
Test the prompt quickly
Built against a specific public prompt, then used the first implementation to identify the larger event-discovery problem worth pursuing.
Organise around a decision
Structured discovery by date and category so someone can move from the open question ‘What should I do?’ to a concrete option.
Build a daily community decision
Built Event of the Day so confirmed members can choose one event from the previous London day, change or withdraw their ballot before midnight, and return to see the community winner.
Preserve the organiser relationship
Kept registration with the original organiser, positioning Astronar as discovery and context rather than an unverified ticketing intermediary.
What happened.
Astronar became a working event-discovery product for London. People can browse upcoming events by date and category, open detailed listings, vote, comment, save events, and continue to the organiser’s page to register.
Building the first version also led to the live Event of the Day feature. From 09:00 until midnight, confirmed members can vote for the best eligible event from the previous London day. Totals stay hidden while voting is open, and the finished result gives the community winner its own reveal and permanent place in Astronar's event history.
What I learned.
Building reveals the better question
The first implementation mattered less as an answer to a prompt than as a way to uncover the deeper discovery and curation problem.
Discovery is a curation problem
More listings are not automatically more helpful; a product needs a credible reason why one option appears before another.
Community signals require provenance
Votes and comments are useful only when people can understand what they represent and when organisers remain accurately credited.
A directory should lead somewhere
Discovery creates value when it helps someone make a decision, which is why the path from ranked context to the organiser’s registration page matters as much as the event list itself.
Related links.
Repositories, demos, event pages, posts, and other places connected to this project.