Roadmap
1. Improving User Experience and Product
This stage makes Lupyd easier and more pleasant to use, based on what real users tell you. It covers faster loading, smoother navigation, clearer onboarding for new users, and fixing the rough edges people report. User experience (UX) simply means how the product feels to use: whether things are where you expect them and whether tasks take few steps.
Work here is guided by feedback loops: collecting reports and suggestions, spotting patterns, then shipping fixes quickly. Performance and reliability improvements also belong here, so the app stays fast as groups and message history grow.
2. Improving Quality of Life
Quality-of-life (QoL) features are small improvements that don't change what the product does but remove daily annoyances. Examples are message drafts that save automatically, keyboard shortcuts, better notification controls, message editing and reactions, pinned messages, and the ability to jump back to where you stopped reading.
Individually each one looks minor, but together they decide whether people enjoy using Lupyd every day. They should follow the minimalist principle: helpful, never cluttered.
3. Federation
Federation means many independent Lupyd servers, run by different people or organizations, can talk to each other as one network, the way email works: someone on one email provider can write to someone on another. A company could run its own Lupyd server while its members still chat with people hosted elsewhere, and nobody depends on a single central owner.
The hard part is keeping the promises Lupyd already makes across servers you don't control. End-to-end encryption must still hold when messages cross servers, roles and permissions must be understood by both sides, and search must still respect who is allowed to see what. That needs an agreed protocol, a shared set of rules for how servers identify each other, exchange messages, and verify trust. Expect this to be the most complex stage.
4. iOS Release
This brings Lupyd to iPhone and iPad through Apple's App Store. The app needs to feel native, with proper push notifications, background syncing, and support for the different screen sizes. Encryption keys should be kept in Apple's secure storage on the device (the Keychain), so they stay protected.
Before release, the app must pass App Store review, which checks privacy disclosures, content moderation rules, and technical quality. A staged rollout, starting with TestFlight (Apple's tool for beta testing), lets a small group try the app first and catch problems before the public launch.
5. More Project Management Tools, With Encryption
Teams don't only chat; they also plan and track work. This stage adds project management tools inside Lupyd, such as task boards, to-do lists, deadlines, assignments, and shared notes, so conversations and work live in one place.
What makes this different from typical tools is that the data stays encrypted. Tasks, comments, and files would be protected the same way messages are, so the server can't read them. That limits some features, such as server-side processing, so each tool must be designed around encryption from the start rather than added afterward.
6. First-Class Support for More Plugins and Extensions
A plugin or extension is an add-on that gives Lupyd new abilities without changing the core app. First-class support means plugins are treated as an official, fully supported part of the product, with stable tools, clear documentation, and the same quality bar as built-in features, rather than an afterthought.