Halo
A Support
Network.
I took Halo from an idea to a working native app: the product strategy, the brand, the design system, the interactions and the SwiftUI build.
- 130.7klines of Swift380 files · 622 SwiftUI views (Build 47)
- 2,058automated tests1,846 unit · 212 UI
- 0.005°Moon accuracyOn-device astronomy, checked against NASA JPL
- 36 × 48presence mosaicAnonymous video that never sends a face
Problem
Give people a reason to return that isn’t another streak to protect.
Approach
Replace the counter with a shared sky. Let people meet without being exposed. Make progress something you keep, not something you can lose.
One person, concept to launch
- Product strategyFramed the problem, set the bet, and cut three versions down to what served it.
- Brand identityVoice, mark and art direction, from Habit Halo to Visual World, Vol. 01.
- Design systemPatterns, colourways, type and the O, reused from app to call to object.
- Interaction designDaily guidance, cohort discovery, voice introductions and turn-taking.
- Native SwiftUIDesigned and built the iOS app, with accessibility and privacy built in.
- Prototype to releaseWorking prototypes, TestFlight builds and the 1.1.0 App Store submission.
- Submitted build
- Halo 1.1.0, submitted to the App Store
- Internal TestFlight
- Built and running, gated, not public
- Working prototype
- Runs in SwiftUI, not in a build
- Concept
- Design exploration, not built
01The product today
Halo 1.1.0,
as it stands.
A daily sky, a cohort that starts together, people you meet by voice and pattern, and progress you keep. Every screen is a capture of the submitted build.
Submitted build
TodayDays sober, tonight’s Moon and one useful move. Starting pointsDay 49 of 365, and the next New Moon to start from. DailyOne prompt for your Circle, answered with a photo. IntroductionsPeople in their own pattern, captioned by their own voice. CircleThis cycle’s Circle: members, the Moon’s phase, conversations.
Halo 1.1.0 App Store captures. Introductions shows a labelled demo profile.
02Product decisions
Three decisions
that shape it.
Each one answers the same question: how do you build a support network people return to, without making them perform, compete or expose themselves?
Anonymous by default
People are recognised by a chosen name and a pattern they design, not a face. A photo is optional, and joining the community never pre-fills a public profile from private notes.
Your style · Halo 1.1.0 People over feeds
There is no public feed. You join a cohort that starts together at a New Moon, its timeline holds only those people, and you meet them through a short voice introduction.
Voice introduction · Halo 1.1.0, labelled demo profile Progress without pressure
Halo counts days without turning them into a streak to protect. Each month earns a stone that stays, and the daily review asks for one useful observation, not a perfect record.
Milestones · Halo 1.1.0
03The celestial engine
A real sky,
read symbolically.
Halo replaced a borrowed horoscope with its own astronomy. The positions are measured, the reading is openly symbolic, and every insight can show its factors. The astronomy is in the submitted build; the language layer is in TestFlight.
Submitted buildInternal TestFlight
- 15.8klines of Swift47 files: the engine and its interface
- 7,064lines of tests23 test files with NASA JPL fixtures
- 0.005°Moon accuracyAgainst NASA JPL Horizons
- 29 sNew Moon timingWorst case against the US Naval Observatory
- Accurate
- The Sun, Moon and planets are computed on the phone in pure Swift, with no third-party astronomy code. A birth chart carries uncertainty windows instead of false precision.
- Benchmarked
- Run against Swiss Ephemeris and Astronomy Engine, it gave the same displayed result in every sampled case. Swiss Ephemeris needs an AGPL or paid licence, so Halo owns its engine instead.
- Explainable
- Hand-written rules write the day, and “Why this insight?” names the factors. Each reading is content-addressed with SHA-256, so it is reproducible and auditable.
- Language layer
- An optional OpenAI layer rewrites guidance from Halo’s own chart facts after the server re-grounds them with Astronomy Engine. It needs explicit consent, runs on reviewed models for an approved cohort, never stores its input, and validates its output before anyone sees it.
- Honest and private
- The reading is framed as symbolic reflection, never prediction. No birthplace is asked for, and birth-chart guidance is opt-in.
- Shared
- Every cohort’s Day 1 is a New Moon, so people start together.
- On device
- Swift
- Foundation calendars and time zones
- SwiftUI
- Observation
- CryptoKit
- Swift Synchronization
- Reference data
- NASA JPL Horizons
- US Naval Observatory
- Server
- Astronomy Engine
- OpenAI, with consent
04The mosaic call
The O holds
the room.
Halo’s live Circle puts each speaker inside the brand’s own mark, as a mosaic of movement. People can be seen without being shown, and heard without being judged by a face.
Working prototypeInternal TestFlight
- Turns, not crosstalk
- Raise a hand for a turn of up to three minutes. Speak, listen or pass; a countdown keeps the floor fair.
- A guide that is a program
- Halo’s guide keeps time and offers a question now and then, as text. It doesn’t listen to the room, and nothing anyone says goes to AI.
- Presence without a face
- In anonymous rooms the camera stays on the phone. Each person is a mosaic of movement inside the O, in their own colour.
- The host decides
- Named rooms (private, 18+) can carry camera video. The host picks Mosaic-only, the default, or Camera-optional for each session.
- Honest about recording
- Halo doesn’t record a Circle, and says before you join that others still could.
Before you joinThe rules, up front. A member is sharingTheir mosaic fills the O, with a countdown. Your turnSpeak or pass. Nobody is put on the spot. You’re sharingYour own mosaic, in your colour. A gentle promptWhen the room goes quiet, a question arrives as text. Thanks for being hereThe O returns, and the meeting closes.
04.1How a mosaic is made
Video presence,
without a face.
In anonymous rooms the camera feed never leaves the phone. On-device vision reduces a person to a grid of movement, which travels as data and is redrawn with Metal on every screen.
The presence lab tunes how that mosaic looks before it reaches a room, tested with synthetic motion rather than a real camera.
- CameraFrames stay on the phone
- VisionPerson segmentation and pose, on device
- MosaicA grid of movement, not a face
- NetworkSent as data, not video
- MetalRedrawn on every screen
Live rooms with mosaic presence run in internal TestFlight and are not public. The Circle meeting above is a working SwiftUI prototype on the same room art, O and Metal shaders, shown with fictional members and no microphone or network.
05Design system
One system,
every surface.
The same few decisions carry the app, the call, the App Store and the brand, so a person is recognisable everywhere and every screen is cheaper to build.
- One identity
- A pattern and colourway carried from Introductions and Circles to call tokens and, in concept, bracelet beads.
- One mark, many jobs
- The horizontal O is the app icon, the call stage and the closing moment of every Circle.
- A type system
- Supermax for the voice and Aeonik Pro for the interface, scaling with Dynamic Type.
- Native motion
- SwiftUI sheets and gestures carry each change; Reduce Motion gets a still, equally clear version.
- Private by default
- Personal notes stay on the device, the community identity is separate, and birth-chart guidance is opt-in.
06Product evolution
Three versions.
One question.
What gives someone a reason to come back that isn’t a number to protect? Each version answered it better, and each one cut more than it added.
The tracker
2025 concept → Sep 2026
Retired
- What it was
- A React Native MVP with a spirit-animal companion chosen from your birthday, a crystal egg tapped once a day, and a streak counter. The first native build counted days sober and borrowed a Sun-sign horoscope from a third-party feed.
- What it taught
- The counter became the product. A streak turns one hard day into a reset, and a borrowed horoscope could not explain itself.
- The decision
- Cut the companion, the spirit animals, the daily check-in and onboarding astrology. Keep the sky, but compute it.
2025–26 MVP · design mockups The celestial engine
October 2026
In 1.1.0
- What it was
- Today opens on tonight’s Moon, a lunar chapter and one move to make. On-device astronomy and hand-written rules write the day; every insight can show its factors.
- What it taught
- A shared, real sky gives people a reason to return that does not punish a miss, and gives strangers the same starting line.
- The decision
- Make the New Moon the start of every cohort, so nobody begins alone.
Today · Halo 1.1.0 The social layer
November 2026
1.1.0 · internal TestFlight
- What it was
- Anonymous identities, cohort Circles, voice introductions and live rooms with speaking turns. In anonymous rooms, video presence is a mosaic computed on the phone.
- What it taught
- Support works when people can be seen without being exposed. Anonymity has to hold in voice and video, not only in a username.
- The decision
- Make the person, not the score, the unit of the product: a name, a pattern and a presence.
Discover · Halo 1.1.0, labelled demo profile
07Brand progression
From healing
to culture.
The product changed what Halo was for, so the brand had to change who it was talking to: from people in crisis to anyone choosing not to drink, and proud of it.
2025
Habit Halo
“Your journey to heal.”
A healing, mystical register: glossy objects, glowing orbs and spirit companions. It spoke to people in crisis, and it looked like every wellness app.
October 2026
Native atmosphere
“Human first. Never alone.”
Generated art gave way to a quiet celestial atmosphere: a Supermax wordmark, Aeonik Pro for the interface, and the Moon as the only illustration.
November 2026
Visual World, Vol. 01
“Sober is cool.”
A culture brand, not a clinic: LL Supermax Square and Aeonik Pro, an O that is always horizontal, and patterns that stand in for a person.
| Aspect | 2025 | Oct 2026 | Nov 2026 |
|---|---|---|---|
| Voice | Your journey to heal | Human first. Never alone. | Sober is cool. |
| Mark | Glossy 3D objects | Supermax wordmark | The O, always horizontal |
| Colour | Glowing purple and cyan | Native celestial gradients | 5 patterns × 10 colourways |
| Audience | People in recovery | People starting over | The sober, the sober-curious and everyone in between |
The brand book
Visual World, Vol. 01.
The art-directed companion to this case study: voice, materials, identity, the product and the objects that might follow, in 34 pages.
Open the PDF34 pages · PDF · 45 MB
Future explorations
An identity you can wear.
A concept for carrying a person’s colourway into an object: a thin bead bracelet on a cream card, with an NFC centrepiece. Fit, NFC, manufacturing and pricing are not validated, and nothing here is for sale.
Concept
Version 01
Woven
Elastic woven bands with the wearer’s colourway on the inside and the O on a leather tab.
Concept render
Version 02
Milestones
The same woven band, now keeping count: a steel stud for each month kept, numbered I to XII.
Concept render
Version 03
Halo Slim
Brushed 316L steel with a blue-green opal at the centre and numbered milestone settings around the band.
Concept render · Visual World, Vol. 01
Version 02 · Packaging
A clear sleeve whose card maps all twelve studs around the O, an activation card that pairs the band with the app, and a single stud with its post.
Concept render
Metal bracelet studies · concept
Beyond the screen
A year
you can hold.
An optional expression of the one-year sobriety commitment.

Physical design studies. Fit, stone retention, and manufacturing remain unvalidated.
Explore Halo.
Explore Halo’s evolving digital experience—from its native iOS interface and anonymous identity system to the visual language connecting product, community, and brand.
Explore the Halo websiteLive preview of the public website at heyhalo.me. The native iOS app is shown above; this frame is not the app.
Design history · 2025 – October 2026The concept archive: the companion, Rooms, SOS and the first native experience, kept as the record behind the decisions above.
Problem
Give people a reason to return that isn’t another streak to protect.
Approach
Make an authored daily world the entry point. Keep reflection optional, support personal, and longer-term progress tangible.
Designed
in SwiftUI.
A daily world. Private progress. Room to reflect.
The earlier native experience
An authored world to enter, progress to return to, and a familiar companion. Inspiration comes before tasks; participation is optional.
Earlier development build · Simulator captures · synthetic profile
Journey Journey
Journey · keep a moment without logging a check-in.
Today Today
Today · chosen support, daily worlds, and weekly progress. Synthetic 14-day profile.
Luna Luna
Luna · a private place to check in and reflect. October 5 Simulator capture.
Product visualizations · supplied October 2026
Earlier technical details
The design continues in code: persistent state, custom scene transitions, accessible layouts, and private on-device reflection.
One source of state
Swift 6, an @Observable HaloStore, and @Environment keep the native surfaces connected. Actor-isolated persistence separates a saved check-in from a private Journey moment.
Native motion & adaptation
A custom AnyTransition brings scenes into focus; Reduce Motion uses a fade. @ScaledMetric and ViewThatFits adapt the calendar to larger type without losing day identity.
Private, optional intelligence
Foundation Models and structured @Generable extraction support local reflection on compatible devices. Memory is inspectable and removable; model unavailability never silently selects cloud.
Foundation Models requires compatible iOS 26+ devices and runtime availability. The native app supports iOS 18+. Journey and Rooms are development previews; the Luna still shows its interface, not generated replies or device performance.
Earlier interaction prototypes · preserved as design history
MVP explorationsA crystal that hatches into a companion.
Early MVP concept boards · design mockups, not app captures
SOS.
Ask for a person before a phone number, and never pretend help is on the way.
- Acknowledged, then reassuring
- The screen says someone is here only after the server acknowledges the request. Queued, ambiguous and delivered stay different states.
- A slider that can't misfire
- 88% travel, one-shot intent, a firm commit haptic and cancellation. VoiceOver gets a semantic button that opens a native confirmation instead.
- Nothing private leaves
- No journal, mood, private text, contact number or health data is posted to a Room. Contact choices live only in view state.
Simulator captures · synthetic data · calling disabled, no request sent.
Need someone? A little company. Emergency help.
Rooms.
Small gatherings around why people come. Local fixture: fictional people, no live connection.
Where Rooms started
The 2025 MVP sketched three kinds of Room around one ritual: hold the Halo to check in, say how you're feeling, then talk in timed turns. Anonymous rooms used spirit characters; open rooms showed friends; the public Welcome Room queued speakers.
Chosen at the door
Private is the default on every entry: Anonymous, with your spirit's species art and no name, photo or profile link. Public shows a first name and photo, nothing else. Leaving removes your presence immediately.
Gatherings Private (default) Public
Reachable navigation
Swipe sideways to step back and down to leave, from anywhere in the Room. A 64-point drag or a fast 24-point flick commits; reversed, tiny or diagonal movement never does.
The first Room
A quiet arrival, then an optional session with an AI facilitator; sharing is never required. A separate Metal study renders the water and a glass Halo with refraction, paused under Reduce Motion.
Progress,
made tangible.
The first physical concept: twelve months, twelve natural stones.
A twelve-setting bracelet accumulates natural stones instead of replacing earlier milestones. A year becomes an object worth keeping.
Physical design details
A twelve-setting bracelet accumulates natural stones instead of replacing earlier milestones. A year becomes an object worth keeping.
A cumulative object
Brushed steel, nearly flush settings, and a serviceable clasp. The digital record and physical object remain separate; a stone cannot certify sobriety.
Still a physical concept
Fit, retention, and manufacturing remain unvalidated; NFC placement is unresolved. The renders show design intent, not finished inventory.
Six stones · earlier milestones stay with you.
Year One · twelve stones, one cumulative object. Design visualization.
Original concept: Sep 2026 – Present (side project). Original concept · native product development in 2026.
Status at this stage: Native app in development · bracelet concept.
Scope: SwiftUI · Native Interaction · Product Direction · Brand & Website · Bracelet & Packaging.
Founder-led product design and SwiftUI development: a daily world, a private companion, and a tangible record of sober progress.
Problem
Give people a reason to return that isn’t another streak to protect.
Approach
Make an authored daily world the entry point. Keep reflection optional, support personal, and longer-term progress tangible.
My work
I founded Halo, set its product direction, designed and built the SwiftUI experience, and carried the same system into web, bracelet, and packaging.


