@!
Zap Now that we've successfully managed to get a few people over the PWA learning curve, I'm working on the next stages of mobile app integration that I laid out in my initial roadmap. The notifications API is hooked up and ready to go, but not yet being used. This is just waiting on a notifications cache so as not to include repeated notifications; and also some tests of various filtering mechanisms so we don't overwhelm your device with stuff like public stream notifications. I'm also currently working on the share API (this is the "Zap to device" share as opposed to the "device to Zap" share that is already fully implemented). And once those are in place, the remaining bits of the roadmap are device authentication (aka fingerprint login to Zap) and building out the client-side browser cache to improve "native app like" performance.
The share API has pretty sucky browser coverage. At this time it's only available on Chrome/Windows/Android and FF/Android and Safari/iOS/OS_X. And it doesn't integrate easily with our existing content Share (share to fediverse). But I'll see what can be done.
There is no timeframe or schedule for any of this essentially R&D work. If you are impatient and need any of this today, you know what to do.
