Any plans for Android? #737

Activity

1. thdxr commented on Nov 1, 2026

   

   thdxr

   on Nov 1, 2026

   Member

   More actions

   Thanks for the question. Here's what we found:

   Android support isn't planned right now. Hex is built as a desktop app for macOS, with beta versions for Windows and Linux, and the roadmap covers only those three. The current work is finishing and testing the new desktop interface on real Macs and Windows PCs, and all releases are paused until that testing is done. Much of Hex depends on things a desktop allows and Android limits or handles differently: global keyboard shortcuts you can hold anywhere, pasting text into whichever app has focus, a running background process with a menu-bar or tray icon, and local models with desktop GPU acceleration. On Android, Hex would most likely need to work as a keyboard (input method) app, which would mean a new app rather than a port of the existing one. Thanks for offering to help: an Android version would be a big design discussion before any code, so the best next step is to describe on the issue how you'd want it to work on your phone.

   — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊

   👍React with 👍1Reacted by Thorn Chorn
2. anthonyamaro15 commented on Nov 1, 2026

   

   anthonyamaro15

   on Nov 1, 2026

   Author

   More actions

   Thanks, that makes sense. Here's roughly what I'd want.

   I already use Wispr Flow on my Android phone. When a text field is focused, a small floating button shows up. I tap it, talk, tap again, and the text gets typed into the field. It's basically the desktop Hex flow with a tap instead of a held shortcut. I think this is possible on Android using an accessibility service, though Play Store reviews those apps pretty closely.

   That said, I'd be just as happy with a keyboard like the iPhone version. If that's quicker to build since the design already exists, it sounds like the better place to start, and a bubble could always come later.

   I'd also like to help out more generally. I'm happy to work on designs for the Android version if that's useful. And since my computer is a Mac and my phone is Android (no iPhone), I could also pick up Mac issues in the meantime. I really like the project and would love to contribute.
3. thdxr commented on Nov 1, 2026

   

   thdxr

   on Nov 1, 2026

   Member

   More actions

   Thanks for the follow-up!

   Starting Android as a keyboard app with a tap-to-talk button gives us a concrete design to discuss, and it would be easier to build than a floating bubble that types into other apps through an accessibility service. What could carry over is Hex's Rust transcription core and its existing toggle-style flow (Shortcut mode › Toggle: press to start, press again to finish), which matches the tap-to-talk, tap-to-type idea. The window, shortcuts, paste, tray and updater are desktop-only, and we'd welcome your Android designs and help with Mac issues in the meantime.

   Things we need to work out

   • The roadmap covers only macOS, Windows and Linux, and every release is on hold until the new desktop interface has been tested on real Macs and Windows PCs.
   • Rune draws Hex's window and HUD on desktop GPUs, and the transcription engine only targets Metal, Vulkan and desktop CPUs, so a phone app would need a new interface and its own model packaging.
   • We couldn't find an iPhone version of Hex in this repo, so there's no shared keyboard design or code to start from yet.

   Questions for you

   • Which iPhone app do you mean as the model: is it a Hex app, and is its keyboard design public?
   • Should transcription run fully on the phone, even if that means a large model download and slower results on older devices?
   • Which Hex features would the keyboard need on day one (modes, text replacements, history), and which could wait?

   We'll take a closer look.

   — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊
4. thdxr

   added

   needs-designFeature that needs a closer look and design before we build itFeature that needs a closer look and design before we build it

   on Nov 1, 2026