The Road Ahead: What's Next for WarpDesk.Space

What we're building next, what we've decided not to build, and how we're thinking about the shape of a family-first product.

Short-term roadmap

Client-side zero-knowledge encryption of vault fields. That's the biggest architectural change on the horizon. It closes the trust gap we described in the privacy article.

Bill parsing

Automatic detection of subscription renewals from inbox mail, linked to vault entries, surfaced on the dashboard as 'renewals this month.' Prototype is running.

Family notifications

Push notifications (mobile web + email) for security-sensitive events: unusual sign-ins, breach alerts on stored services, expired 2FA.

What we're not building

Family location tracking. Content filtering. A native mobile app before the web version is exhausted. Enterprise SSO. Business plans.

A native app, eventually

Mostly to unlock better background sync and biometric unlock. Not a priority until the web version has hit its ceiling. It hasn't.

Cross-family sharing

The ability to share a single entry with someone outside your family (a neighbor watching your cat needs the Wi-Fi). Small scope, useful.

Open questions

How much of the household's finance surface should live in WarpDesk versus stay separate? How aggressive should breach alerts be? We're listening.

What we've heard from users

The single most requested feature is per-entry sharing outside the family. Second is a cleaner bill-splitting flow. Third is better import from LastPass.

A worked example of philosophy

A power user asked for CLI access. We declined — a CLI is a business-tool feature. It doesn't fit the household frame.

Wrap it up

The next year is about depth, not breadth. Making the four surfaces we have (vault, inbox, family, credits) genuinely excellent. New surfaces come after.