Selected work / Personal prototype / AI-assisted product development
Night Out: an outing request became a useful guide.
A personal planning request grew into a mobile itinerary, a spoiler-free guest edition and a clearer way to discuss group costs before booking.
- My role
- Brief, constraints, product direction and owner review
- Built with
- Artemis, HTML/CSS/JavaScript and AGY-generated media
- State
- Working private prototype. Service and travel expansion under consideration.
01 / The problem
A list of places still leaves someone doing the work.
I wanted an evening I could open on my phone and follow. That meant reconciling dated activity and movie listings, arrival windows, dinner timing, optional stops and the number of people coming. A venue being open is not the same as a session having room for the group.
The useful output was one practical sequence with sources and unknowns kept visible. Published availability was never treated as held inventory, and nothing was purchased automatically.
02 / The decisions
Real constraints changed the design.
Two genuinely separate editions
The organizer keeps vendor details and operational notes. The mystery guest edition keeps the instructions and clues but leaves the actual surprise out of the file, source, links, print and download.
It does not hide the answer in a collapsed panel or a reveal button.
A fresh Saturday plan
One participant could only join on Saturdays. The original afternoon time did not have enough capacity on the new date, and the movie times differed too.
Fresh research changed the activity time, moved dinner after the film and changed the later route. This was a researched revision, not an automatic date swap.
03 / What exists
A guide that can be used, printed and saved.
Working in the private guides
- Sequenced stops, arrival targets, route links and explicit uncertainties.
- Known-cost subtotals for different group sizes.
- Optional late-stop routing and practical preparation checks.
- Organizer and spoiler-free guest editions, light/dark themes, print and standalone HTML exports.
Not implemented
- Live travel, restaurant or cinema APIs.
- Reservations, purchases or automatic coordination.
- Participant-specific activity allocations or fixed-cost split rules.
- Payment collection, a paid/owed ledger or reimbursements.
04 / Try an anonymous sample
See the known subtotal change with the group.
This public-safe sample recreates the existing headcount calculation with anonymous content. It is a functioning control, not an image of an expense app. The private family guide is not published here.
Activity + optional dinner
Historical research snapshot: activity $39.99 per person; optional dinner $39.95 per person.
- Known group subtotal
- Known items per person
- $79.94
Activity + optional dinner only. Not a current quote and not the whole-night price. Movie tickets, tax/tip, fees, transport and other optional costs are excluded.
Known subtotal for 4 people. Enable JavaScript to change headcount.
Everyone in this sample joins both priced items. Choosing participants activity by activity, handling unequal shares and tracking who has paid are future ideas, not hidden capabilities of this control.
05 / How I worked
Product direction with an AI-assisted build.
I supplied the goals, personal constraints, design direction and review decisions. Artemis handled research, implementation and verification. AGY produced the illustrative campaign imagery and copy drafts that were reviewed against the actual project history.
The implementation uses ordinary HTML, CSS and JavaScript. Python and browser tooling supported media/export preparation and checks. The public portfolio sample keeps the cost calculation small and testable rather than presenting a mock payment workflow as a product.
The private-guide checks covered group size, optional routes, mystery interactions, themes, print and saved HTML. The public calculation has separate arithmetic and invalid-input tests. Responsive browser checks are not a claim that every physical device or vendor checkout was tested.
View the generated origin-story infographic
06 / What this could become
Make the planned share clear before anyone commits.
A group trip is not always an equal division. Someone may skip an activity, join a day late or share a room. A useful next step would show each person's planned share based on what they are joining, then keep actual charges, deposits, refunds and reimbursements separate.
I am also considering a narrow manual planning service, branded guest guides and eventually better-sourced travel information. Demand, delivery effort, pricing and the authority needed for coordination still need testing. No booking or payment service has launched.