fae

usefae.com

fae

A software studio

Fae is a software studio. It designs and builds web and mobile products end to end: the design, the code, the infrastructure, the words on the buttons. Then it keeps them running after they ship.

Six products currently shown: some live and maintained, the newest still in development. Each does one job for one kind of person. They are set below at full scale: the problem, the decisions that mattered, and what each one looks like in use.

Specimen №01

Web + macOS + Windows + Linux · 2026–present · Waitlist

Bellhop

Printers and scales for web apps, with no one in the middle.

Local printing and USB scale reading for SaaS products: a desktop agent, server libraries, and a licensing backend that stays out of the data path. Labels print with no browser open and nobody logged in.

Platform
Web + macOS + Windows + Linux
Years
2026–present
Built with
Ruby on Rails · Swift & SwiftUI · WebSockets
The Bellhop menu-bar agent on macOS: online, connected to Slaydate, nothing printed yet.
Fig. 01: The agent at the desk, online. From the app.

Specimen №02

Web · 2025–present · Live

Slaydate

Event logistics for people who run in-person Blood on the Clocktower games.

An events platform for in-person Blood on the Clocktower games: public signups, ordered waitlists, multi-room seating, door check-in, and post-game recaps.

Platform
Web
Years
2025–present
Built with
Ruby on Rails · Hotwire · PostgreSQL
The Slaydate event editor: A Lazy Sunday Bloodbath at Hillcrest Community Centre, with event artwork, a map, times, and a description.
Fig. 02: Editing A Lazy Sunday Bloodbath. From the app.

№02 ↔ №03: these two talk to each other. Scan a QR code and the night's roster loads into the storyteller's iPad; when the game ends, the log flows back for recaps.

Specimen №03

iOS · 2025–present · Live

Blocktower

A storyteller's toolkit for running Blood on the Clocktower games.

For things the Grimoire can't track, Blocktower give storytellers vote counts and tracking, dead votes, phase management, timers and a game log at the end.

Platform
iOS
Years
2025–present
Built with
Swift · SwiftUI · WidgetKit
Blocktower on day one: a nomination dragged from Erica to Corina across a ring of wax-seal player tokens.
Fig. 03: Day one, a nomination dragged from Erica to Corina. From the app.

Specimen №04

iOS · 2026 · In development

Whispers

Structured game state, derived from notes written in plain language.

A note-taking app for Blood on the Clocktower players that reads your free-text notes and derives who claimed what, who suspects whom, and who died when.

Platform
iOS
Years
2026
Built with
Swift 6 · SwiftUI · SwiftData
Whispers mid-game: a note stream with role names and player mentions highlighted in colour.
Fig. 04: Notes in, structure out. From the app.

Specimen №05

iOS + tvOS · 2026 · In development

IV

Four threads, one finger, and your own path as the hazard.

An arcade roguelike about flying four glowing threads in formation with a single finger, threading them through their own wake while a deck of fifty upgrade cards reshapes every run.

Platform
iOS + tvOS
Years
2026
Built with
Swift · Metal · UIKit
IV mid-run: four neon threads curving inside a circular hex arena, a whorl waiting, upgrade slots filled.
Fig. 05: Four threads aloft. From the app.

Specimen №06

Web · 2026 · Live

Thufir

Who holds what, in a game built on not knowing.

A companion for the Dune board game that tracks the Treachery deck: what was bid, who holds what, what remains, and the cards nobody has seen.

Platform
Web
Years
2026
Built with
Stimulus · Tailwind CSS · Local storage
Thufir's setup screen: six Dune factions with player names filled in, ready to start.
Fig. 06: Six players ready. From the app.

Appendix A

Four working rules

The approach

Narrow beats broad.

Every product here does one job for one kind of person. The roadmaps are mostly lists of things they will never do. That's what makes them good at the thing they actually do.

The constraint is the design.

"One-handed, in a hurry, on a bus" isn't a nice-to-have. It's the thing that decides what gets built. Real usage conditions come first and the feature list falls out of them, not the other way around.

Boring technology, deliberately.

Rails and Hotwire on the web. Native Swift and SwiftUI on iOS, with as few dependencies as possible. The optimization is for what still compiles and runs in five years, not for what's interesting this quarter.

Shipped, then maintained.

Launching is the cheap part. Everything Fae has shipped is still running, still getting fixed, still used by people who say directly when something is wrong. That feedback loop is the whole point.

Colophon

Set in Silkscreen, Libre Franklin & Fragment Mono

Tim Sullivan

I'm Tim Sullivan.

I've been building software professionally for a long time. Fae is the small studio where I do it now, mostly its own products, occasionally something for someone else.

The best way to judge the work is the work itself. The write-ups explain how each product was made, including the parts that were hard.

Correspondence

Fae is mostly heads-down building the things above. If you'd like to say hello anyway: hello@usefae.com