# Roadmap Where Phlip is, honestly. Status as of July 2026. ## Shipped | Area | Status | |---|---| | Card-hand pitching (flick/drag, drafts, undo, presets + drawn custom cards) | ✅ | | Open Pitch mini-game (all four resolution modes) | ✅ | | Timeline (month/week/day), fuzzy times, event chains | ✅ | | RSVPs with live attendee lists, reactions (incl. drawn), notes | ✅ | | Upcoming flick deck · Memories (local-only photos) | ✅ | | Personal space + multi-server client | ✅ | | Multi-server hosting on one phone, local discovery | ✅ | | Public hosting via Cloudflare Tunnel (trial + own-domain) | ✅ | | Per-user login: passwords never sent over the wire; content encrypted with AES-GCM-256 (partial - see Encryption below) | ✅ | | Host approvals, member directory, roles (host/admin/mod/user/viewer) | ✅ | | WhatsApp share of event card image + deep link | ✅ | | Themes: light/dark with animated transition, server card themes | ✅ | | Supporter cosmetics (never gate features) | ✅ | | Daily-driver hosting polish | ✅ | | Public event microsites | ✅ | ## Next ### Open-source hosting backend (Apache-2.0) Publishing the hosting backend - the server that runs on the host phone and holds your group's data - as **open source under the Apache License 2.0**, so it can be independently read, audited and self-built. The app and client stay proprietary; the [[Notices/Licence|Licence]] page sets out the split. ### Encryption (in development) Phlip encrypts message and event content today, but it is **not complete or dependable yet**: some metadata isn't covered (time fields, names, icons, routing, pending-join IPs), LAN connections can be unencrypted, and it needs specialist security review. This is the main security workstream - until it matures, please don't rely on it. The [[FAQs]] state the current boundary plainly. ### Chat bridges (WhatsApp & Discord) Connecting a Phlip server to a WhatsApp chat or Discord server - so messages become events and RSVPs post back - is planned but not yet built. Today you can share an event as a card image with a join link; deeper two-way bridges are future work. ### Calendar integrations Connect Phlip events to your daily calendar app to seamlessly sync your work and social life whilst keeping them distinct. ### Ship it properly Publish the full Android app, then an **iOS client** (browser access is the interim path for iPhone friends). ### Improve location options Currently this relies on user input, ideally we can link to a map services without impacting data protection and integrity of the app's functionality. ### Backup servers To mitigate risk of lost data, allow servers to have a backup. Likewise servers will be exportable and importable for full content or structure (e.g. custom event types) to replicate servers for multiple groups. ### Custom server styling Support for custom css per server to give hosts identity. ### Improved haptics and sound effects Possibly even custom options to improve feel of scrolling and flicking cards. ### Further hosting enhancements We would like to expand hosting options as this develops so that it could support larger groups on more devices. ## Not planned - Photo uploads in chat or event galleries - chat stays coordination-only; Memories photos stay on your device. - Feature paywalls - supporter purchases are cosmetics only. - Notifications - Phlip exists to be be browsed when you are ready, in your own time. --- **Next:** [[FAQs]] · [[Guides/1. Start here]] · [[Notices/Legal]]