Destination-aware discovery
Members can indicate where they live now and where they expect to be, then discover people with compatible timing and interests.
Flagship blueprint · Worked example
A dating product for people who feel at home in more than one place. This example shows how a customer idea becomes a portable specification before an agent changes the code.
Use this as a starting point“I want to create a dating app for people who enjoy travelling and living abroad.”
Product decisions
These are proposed product requirements. An implementation agent must map each one to the real pH7Builder codebase rather than assume the exact field or module already exists.
Members can indicate where they live now and where they expect to be, then discover people with compatible timing and interests.
Exact location remains private by default. Members control whether travel plans are hidden, approximate or visible to matched people.
Languages, travel pace, work pattern and shared interests matter alongside existing profile and matching preferences.
Reporting, blocking, moderation and clear community rules are launch requirements, not work deferred until after acquisition.
Portable specification excerpt
product:
name: "Nomad Connections"
purpose: "Dating for travellers and expats"
audience: "Adults aged 18 and over"
foundation:
package: "ph7software/ph7builder"
version: "19.4.0"
experience:
discovery:
- "current city"
- "preferred destinations"
- "languages"
- "shared travel interests"
privacy:
exact_location_sharing: false
travel_dates_visibility: "private by default"
requirements:
- "Members can discover compatible travellers."
- "Members control their location visibility."
- "Members can report and block another account."Important: this schema records product intent. It does not claim that every key maps directly to a current pH7Builder configuration setting.
Make it yours
Start with a portable blueprint, then install and customise the open-source application with your preferred AI coding agent.