After 4 years and many customer requests we are finally launching our native iOS and Android apps + Browser Extensions for Google Chrome, Firefox, Safari and Edge
@peer_rich congrats on the launch! 🚀 As someone who's tested practically every scheduling tool out there, you're setting the new standard for what these platforms should be. Already loving the app and excited to see where you take it.
@peer_rich — The “one codebase” move (Expo + WXT) + Gmail/Calendar injection is a super pragmatic distribution bet.
At scale, the gnarly part is state sync + idempotency (no-shows, reschedules, reminders) across extension/mobile with flaky networks—best-practice is durable background jobs + optimistic UI + server-enforced idempotency keys + push (SSE/WebSockets) for near-real-time updates.
Open Q: how are you sharing auth/session + permissions safely across the injected surfaces, and will Live Activities/widgets be driven by push events or periodic refresh?
Honestly surprised this took only 4 years considering how hard good scheduling UX actually is The browser extension integrations like injecting links directly into Gmail and handling no-shows inside Google Calendar feel way more useful than just having a standalone scheduling app.
Also really cool that the mobile apps + extensions share the same codebase. Curious how you balanced cross-platform consistency while still keeping the apps feeling native on both iOS and Android.
Replies
Cool, thanks!
Only works with cal.com, not with cal.eu, correct?
@peer_rich Can you confirm that briefly?
Edge Up Sports
@peer_rich congrats on the launch! 🚀 As someone who's tested practically every scheduling tool out there, you're setting the new standard for what these platforms should be. Already loving the app and excited to see where you take it.
Inbox Zero
love it!
When can we expect to see the app available in Apple Bussiness Manager for managed devices?
Pawpal
letsfuckinggggoo!
@peer_rich — The “one codebase” move (Expo + WXT) + Gmail/Calendar injection is a super pragmatic distribution bet.
At scale, the gnarly part is state sync + idempotency (no-shows, reschedules, reminders) across extension/mobile with flaky networks—best-practice is durable background jobs + optimistic UI + server-enforced idempotency keys + push (SSE/WebSockets) for near-real-time updates.
Open Q: how are you sharing auth/session + permissions safely across the injected surfaces, and will Live Activities/widgets be driven by push events or periodic refresh?
Please note: does not work with cal.eu.
Honestly surprised this took only 4 years considering how hard good scheduling UX actually is
The browser extension integrations like injecting links directly into Gmail and handling no-shows inside Google Calendar feel way more useful than just having a standalone scheduling app.
Also really cool that the mobile apps + extensions share the same codebase. Curious how you balanced cross-platform consistency while still keeping the apps feeling native on both iOS and Android.