What's coming, what isn't
One page holds every promise, so you never have to piece the plan together from scattered hints. Nothing has a date; a date here would be a guess dressed up as a commitment.
Planned, in rough order of likelihood
Updates ship through the app itself, so most of this arrives without you doing anything.
Public launch
Aphotic has not launched. The app and the store both work, but nothing is for sale until we say so, which is why the store shows no plans right now. The download is there for people testing with us. When we open, it happens here and in the store on the same day.
The store today →Google Play listing
A second way to install, for people who don't want to install a file by hand. It's the same app with the same encryption, and you'd still buy the license in our own store. The direct download stays the main, private route. If the listing ever gets pulled, nothing else changes.
How installing works today →Media in Community chat
Community chat carries text today, and marketplace listings already carry photos. Photos, voice notes and files in the chat itself work in direct messages and small groups; carrying them into Community chat is next on the list.
What Communities are →Video calls
Voice calls between contacts work today. Video comes next, through the same call relay with the same two layers of encryption. Video can't be sent at a constant rate the way voice is, so the amount of data a video call sends says more about what is happening on screen. We'll spell that out when it ships.
How voice calls work →Publishing the cryptography source
The pages exist: the exact Kotlin files behind the handshake, the ratchets, the sealed-sender envelope and the group core, served straight from the repository. What is still open is the license they go out under, and that decision has to come before the pages do. Until then, the protocol page prints the function behind each construction, cut from the source at build time, and the app itself is what you can inspect.
The security design →What we are not building
Absences with reasons, so you don't wait for something that isn't coming.
An iOS client
There is no iOS app and we're not promising one. One operator can do one platform properly, and a half-finished second one would cost exactly that care. If this ever changes, it changes here first.
Typing indicators
We never built a way to send them and we're not going to, so nobody can see when you started typing.
Cloud anything
There is no cloud backup and no cloud sync. The one thing a server keeps past 7 days is the encrypted history of a Community whose founder switched that on.
Missing something you'd pay for?
Tell us. The plan above is a judgment call, and judgment can be argued with.