Through

Through has an unusual success condition for a digital product: brief use followed by meaningful action away from the phone.

The intended experience is a small private space where a young person can choose something they want, make a manageable commitment and look back honestly without entering another feed.

The early working title explained the product direction, but sounded more like positioning than something a young person might own. Through carries the action at the centre of the idea: choose something real and see it through, then get back to your life.

I treated the naming decision as more than visual branding. Public copy, consent language, email display identity, Figma, tests and production moved together before the first campaign signup. Stable URLs, provider resources, campaign constants and dated evidence remained unchanged where renaming would add risk rather than clarity.

The working thesis connects a chosen real-world action, a light-touch commitment and non-punitive reflection. The product should never turn missed intentions into shame or optimise for time spent inside the app.

That principle is firm; mechanics such as goal limits, notification cadence, coaching tone, streaks and rewards remain open to evidence.

The production refinement retained the orbit as the landing page's main visual motif: three restrained rings and three points, exported directly from Figma rather than approximated in CSS.

It scales from 340px on mobile to 480px on desktop, moves slowly and becomes static when reduced motion is requested.

The live experiment is a Republic-of-Ireland availability waitlist for adults aged 18 or older, not a beta or youth research cohort. It asks for the minimum needed to send one message if Through becomes available.

The campaign has fixed dates, explicit consent, stated deletion controls and no analytics, profiling or newsletter sequence. That makes the experiment real without pretending the underlying product has been validated.

The proposed trust model treats personal reflection as sensitive data. It prioritises clear consent, data minimisation, age-appropriate safeguarding and careful escalation, while keeping AI support bounded in tone and purpose.

The adult waitlist implements a narrow privacy boundary, but no youth-facing collection or safety system exists. Those broader safeguards remain requirements to investigate and validate.

The public pitch, coherent identity and adult waitlist make the direction discussable, but visual coherence and deployment are not participant evidence.

The next gate is research with intended users and age-appropriate safeguarding expertise to test the problem, language, trust expectations and smallest credible experience before application development begins.