Roadmap · honest about what's where

v1.0 is the considered launch,
not the minimum-viable release.

Most apps ship v1.0 the moment a single happy path works, then patch their way to confidence. Lanai's brand thesis requires that the first release feel complete and finished. The build runway is eighteen to twenty-two sessions across eight feature tracks, and the considered launch is what's listed below — not a six-month roadmap masquerading as a 1.0.

No public dates. We ship when each track is ready and the audit cadence comes back clean. If you want a notification when v1.0 enters the open beta, the porch's mailing list is the one place we send anything.

01

v1.0 considered

v1.0 — the considered launch

Eighteen to twenty-two build sessions across eight feature tracks. The first release feels complete and confident, not minimum-viable. These are the features that promote from v1.x into v1.0 because the brand thesis requires they ship together.

02

v1.x

v1.x — the next chapter

Features on the table, not on the calendar. Each ships when it earns the right — when the principle test passes, the audit cadence catches no regressions, and the engineering investment is honestly worth it.

Live v1.x

Jetstream live updates.

Live feed via the AT Protocol's Jetstream firehose. Opt-in, deliberate, battery-conscious. Deferred from v1.0 so we can do the WebSocket lifecycle work properly rather than as a side quest.

Intelligence v1.x

Feed variety shuffle.

Reorder Following to spread same-author and same-topic posts. The set is fixed by your choice; AI changes the order, never the contents. Setting: chronological (default) or mixed-variety. Indicator visible whenever shuffle is active.

Intelligence v1.x

Quiet content overlay.

On-device classification adds a tap-to-view friction for distressing or graphic imagery. Never silently filters. Always your choice to view. User-configurable for what to gate.

Intelligence v1.x

Inline translation, on demand.

Apple's on-device translation, invoked per post. Detects language; offers translation when it differs from your preferred languages. Never auto-translates.

Intelligence v1.x

Topic clustering in saved posts.

Group your saved-for-later posts by inferred topic, on device, after the save event. You see clusters as suggestions you can accept or ignore — never the only way to view your saves.

Postcard v1.x

Stationery variations (Pro).

Library Card, Recipe Card, Magazine Clipping. Each a complete restyle of Postcard Mode within the same metaphor family. Pro-tier unlock; the base Postcard Mode stays free.

03

v2 territory

v2 territory

Bigger architectural moves. Worth tracking, not worth committing to yet. We mention them so you know we know they're coming.

Auth v2 territory

OAuth via ATOAuthKit.

When the AT Protocol's OAuth story stabilizes, Lanai migrates from App Password to ATOAuthKit plus ASWebAuthenticationSession. Until then, App Password keyed by DID — handles change, DIDs don't — is the honest choice.

Editorial v2 territory

Core Text-based Reading Mode.

If editorial Reading Mode earns the engineering investment, drop to Core Text for the renderer. Tighter optical control, line-breaking that respects rivers and widows — the kind of typesetting nobody else on Bluesky is doing.

For the curious

The eight feature tracks.

Lanai's roadmap is organized by track, not phase. Tracks run in parallel; a feature in v1.0 from one track doesn't block work on another. The tracks are: Reading (timeline, Reading Mode, Postcard Mode), Compose (composer, thread builder, alt-text suggestions), Profile, Notifications, Curation (custom feeds, mute lists), Settings, Export, and Intelligence.

The audit cadence is the load-bearing piece. Per release, every AI feature is checked against the six corollaries. Every theme is rendered at AX3. Every layout is verified at all twelve Dynamic Type sizes. Failing any audit means the feature waits.

Honest constraints

What we know we can't promise yet.

OAuth is v2 territory.

v1 ships with App Password authentication keyed by DID (handles change; DIDs don't). When the AT Protocol's OAuth story stabilizes, Lanai migrates to ATOAuthKit. We say "v2" because we don't know when that is, and we'd rather not promise a date.

No release date for v1.0.

The runway is eighteen to twenty-two build sessions. The "session" unit is loose on purpose — it's how we work, not a clock. We'll announce the open beta when it opens, the public release when it ships, and not before.

Pricing is decided closer to launch.

The studio pattern is one-time purchases. If we ship anything subscription-shaped, it'll be for a feature with a real ongoing server cost — not a license to keep using software you already paid for. Free tier is real.

The mascot is not negotiable.

Windy presides over empty states, launch animations, the About screen, and the occasional quiet corner of the app where a small dog belongs. The roadmap will not, at any point, contain a task to remove her.

For the porch's mailing list.

Drop a note. Tell us which platform you're on and how you read Bluesky now. We'll let you know when the open beta lands.