Official Website: https://app-suite.eu/talkforward
Get It On Google Playhttps://play.google.com/store/apps/details?id=eu.appsuite.talkforward
Talk Forward is a free, high-performance Android screen reader designed from the ground up for speed and responsiveness. Built by the same developer behind AGram, it features an iOS-inspired gesture model that prioritizes simplicity and immediate feedback, making it an excellent choice for users looking for a more "native" experience on Android.
Core Features
- Simplified Gesture Model: Say goodbye to complex L-shaped angle gestures. Talk Forward uses a single-finger swipe model (left/right for navigation, up/down for the rotor), making interactions faster and less prone to errors.
- VoiceOver-Style Rotor: A two-finger rotation gesture allows you to quickly cycle through navigation granularity, speech rates, or custom voice profiles.
- Voice Rotor: Define and store multiple complete voice profiles (engine, rate, pitch, volume) and switch between them instantly—perfect for toggling between a fast voice for skimming and a clearer voice for reading.
- On-Screen Braille Keyboard: Supports 6 or 8-dot input directly on the screen, with both dedicated input modes for typing and command modes for system control.
- Hold-to-Dictate: A seamless way to dictate text—simply press and hold a finger on any text field to start. Talk Forward stays silent while recording to prevent misinterpretation, and you simply lift your finger to commit.
- Customizable Two-Finger Gestures: All four two-finger swipe gestures are fully reassignable, allowing you to map them to Home, Back, Notifications, Quick Settings, or whatever best fits your workflow.
- Edge Gestures: Slide in from the bottom for Home/Recents or from the top for Notifications/Quick Settings, complete with vibration and spoken cues for confirmation.
- Optimized Latency: Heavily optimized for speed, ensuring that gestures and speech respond in milliseconds for a smooth, fluid experience.
Getting Started & Support
Talk Forward is free to use and provides in-app updates directly from the settings menu.
Hep Center & Changelog For guides on how to create scripts and sound packs, be sure visit the Talk Forwward Help Center For the latest release notes, dive into the Talk Forward Changelog
Support the Project: While the app is free, users can become "Supporters" to help fuel development. Supporters receive a "Talk Forward Gold" badge within the app.
- Community: The developer is highly active. For those looking to keep up with development or share feedback, keep an eye on this thread and the Blind Android Users Telegram group./
Quick Tips (Community Insights)
- Opening App Lists (Samsung): If the standard two-finger swipe up doesn't trigger the app list, you can remap this in Talk Forward Menu > Edit Gestures. Assign "Synthetic Swipe Up" to the gesture.
- Switching Screen Readers:
- Samsung: Use the accessibility shortcut (often Volume Up + Power or a long hold on volume keys) to toggle between screen readers.
- Pixel: Use the accessibility shortcut or a triple-finger tap on the screen.
- Braille/Emojis: There is no direct emoji insertion in the current Braille keyboard. To insert an emoji, hide the keyboard (two-finger swipe down) or switch back to your primary keyboard (three-finger swipe down).
Comments
I imagine... Re: three finger rotor
Pure speculation here, but I imagine this is activated by pressing three fingers on the screen, keep the middle finger stationary, while sliding your index finger up, and your ring finger down.
HTH. 😅
Three finger rotor
This doesn't seem like a bad idea, but not sure I'd use it. If you use different rotor groups, then you might use the three finger rotor to jump between those.
three fingers rotor
Hi everyone,
actually you can assign it to whatever you want, so if you'd like to use that to raise/lower the volume, you can. or should you want to assign the three fingers rotor left to an action and the fingers right one to a completely different one, it's also possible.
Latest Talk Forward Observations
And so,
I understand how the three-finger rotor works.
You turn all three fingers clockwise or counterclockwise.
In addition, for either version of the rotor gestures to work easier, you may wish to unassign the two-finger groups actions and change them to something else. Or use the three-finger rotor for groups and keep the two-finger rotor gesture actions as they are by default. Or change the rotor actions to the two-finger left/right swipes.
At least on my phone with a screen protector, it works better that way.
As for the Talk Forward keyboard...
The only issue I have with it, is that it doesn't defult to, default. It defaults to characters. It should be defult, then you can cycle to characters if needed. Or if you're in an edit box, then I guess characters may may more since. But not outside of it. But then again, the enhanced keyboard with browserse mode uses arrorws going by letters and not by the default element. So, I'm not sure which is right.
Can't waitron try and make a voiceover keyboard layout since I found the scripting instructions. I never dealt with LUA before. Shouldn't' be too hard.
Almost forgot to mention, the practice screen currently doesn't have all talk forward bindings yet. I guess that's in the works?
Version 26.7.11 is available (Non-Play Store)
• Stability, at depth: until now, a single failing feature could switch the whole screen reader off. A user reported Talk Forward restarting over and over on their Xiaomi after a reboot, before the first unlock — the cause was the translation feature crashing because its language models cannot start at that point. Rather than fix that one case, we went through everything that runs in the background or reacts to a gesture and put a net under it: a failure now costs the feature involved, never the reader. In practice that covers every gesture, every rotor entry, every menu, every accessibility event, and some thirty background tasks.
• Translation: when its models cannot start, it says so instead of stopping the reader.
• New, in beta: screen recognition. Some apps expose nothing usable — a game, a drawn view, an unlabeled button. Talk Forward can now rebuild what is on screen by combining what the app does reveal of its geometry with what text recognition reads from the pixels, then let you move through that model by swiping and activate by double-tapping. You switch it on app by app, from the "Screen recognition" rotor entry, and it stays inactive everywhere else. Text recognition runs offline and free for everyone; supporters additionally get AI analysis and a shared cache, which names silent icons once for every user. This is a first version: explore-by-touch is not available yet, and protected screens (banking, PIN entry) cannot be analyzed. Feedback welcome.
Also included since the previous stable release:
• Voice: fixed the reader going completely silent after a reboot when the speech engine (e.g. Vocalizer) failed to start — it now recovers automatically, falling back to eSpeak if needed.
• More robust startup: if an optional feature fails to start (device-dependent), the reader still comes up with at least speech and touch.
• Three-finger rotor: a new rotor alongside the two-finger one — the middle finger pivots while the outer two rotate around it.
• Field-aware letter keyboard: a dialpad for number fields and PINs, a number row for passwords, and @ and .com keys within reach for e-mail and web addresses.
• Calls: the answer/end-call gesture now works with WhatsApp, Telegram and Signal calls too, not just carrier calls.
• Physical keyboard shortcuts: the Alt key (left or right) can be used as the keymap modifier.
• Italian braille: updated comp6 table (Monza standard).
• Volume keys: fixed them sometimes feeling dead — they only move the cursor when the keyboard is actually up, otherwise they change the volume as before.
• New "Add to clipboard" action (assignable to a gesture): appends the focused item's text to whatever is already on the clipboard — fire it on several items to accumulate them.
• Braille keyboard: three-finger-up "send" no longer sometimes switches conversation instead of sending in some apps (e.g. Google Messages' web view).
• The braille/letter keyboard no longer triggers unwanted screen rotation.
• Updated for the latest Android and Google Play requirements.
As For 26.7.4 On The Play Store...
It's a dilemma!
Is it better to become a Talk Supporter from the play Store or is it better to go the PayPal route. I myself can do either one of said mentioned options honestly. I've been just waiting for the right calling on wish one to go with.
Incentives?
Any incentives supporting the Dev through the play store, versus going the PayPal route, as you hinted above? Or is this simply a Trenton Matthews dilemma? 😛
Re: Incentives?
Honestly?
Going the play store route means I get points for purchasing (particularly since I have Play Pass for an entire year).
So, the question then is:
If I have the play store version of Talk Forward on one phone, but the non-play store version on another phone, do I have to do a onetime payment for each phone?
Which I do not mind doing.
Fair enough
The dev may be able to work with you on that, however. 🤷
Lemon Squeezy
I donated via the website which used Lemon Squeezy at the time, then installed via PlayStore. I then did not see an immediate way to tell Talk Forward I was a donor. So it is indeed likely the better approach is to use the payment via the method you intend to install. Also possible I overlooked something or the feature is getting updated. Figured I'd worry about it later. I wouldn't have bothered to share this but in case it helps you...
Re: Lemon Squeezy
Ah, thanks for sharing!
Yeah, that does help.
about supporting Talk Forward
Hi,
Depending on whether it is installed from the website or from Google Play, the license mechanism is different, and currently not linked between the 2 platforms.
This is something however that could be useful, so that a supporter using the play store could easily migrate to the website version, which is often more recent due to google's review time, without having to loose his/her license.
I'll implement that for a future version.
As for whether it's better to support it from GPlay or the website, it's really up to you? ;)
26.8.1 is out!
Talk Forward 26.8.1 — the visual agent
You know that screen. The one where a button is called "button", where three pictures all sound alike, where the app lets you go round in circles without ever telling you what is in front of you. Usually, at that point, you ask someone.
From this release, you can ask Talk Forward.
You tell it what you want to do — "press send", "open settings", "tick the box at the bottom of the screen". It looks. It searches for the matching control. Then it tells you what it found, and it stops there. Nothing fires until you confirm with a two-finger double tap. That is deliberate: an agent that presses buttons you have not seen is not help, it is a risk.
And if the screen moved between the moment it looked and the moment you confirm, it says so and presses nothing.
What really changes is that it does not depend on the app's goodwill. Where accessibility is sound, it uses it. Where it is missing or broken, it takes a screenshot and analyses that — without your having to enter any special mode. It is not a mode you turn on, it is an action, just like "describe the screen". Run it from the Talk Forward menu, or assign it to the gesture of your choice.
One case in particular, and not a small one: image CAPTCHAs. "Select all images containing a traffic light." Pressing is the wrong answer there — several cells, in order, on a screen that changes by design after every click. So the agent describes instead of pressing. It reads the grid out cell by cell — "row two, column three: a red bus" — then repeats the list of matching cells at the end. You do the pressing, one at a time, with an ordinary double tap. You stay in control from start to finish.
When the answer is text to enter rather than a button to press, the agent puts it on the clipboard and tells you; all you have to do is paste. A "type the text" action will come once identifying the right field is reliable.
The visual agent runs on our servers, and it is reserved for people who support the project. Every request has a real cost, and your support is what pays it. Everything else in this release is for everyone, as always.
This is a first version, and your feedback matters: tell us where it got you out of trouble, and above all where it got it wrong.
Also in 26.8.1
Available now: in-app update for the version downloaded from the site. The Play Store build is with Google for review, and will roll out on production and beta as soon as it is approved.
Nice work!
Downloading this RIGHT NOW! Nice work! I'm quite excited for this.
@Justin
Tasking you with writing a summary of this latest build, I know you have a Pixel, rather than a Samsung, but I still wanna hear how well this new version is working out on Android. I so can't wait to have my new device.
Lemon Squeezy obviously Doesn't Make Blueberry Lemonade
, but it sure makes a difference when supporting a program, you use every day.
Especially since I adore the color gold!
@Brian
Hmmm, what I can say. All gestures are working well on my Pixel. Performance is great, nowhere near the lag of normal Talkback. With the visual agent and the screen recognition I'd say they both have potential but are still in early development. I have an app for example that was not written with native Android controls or UI elements, and while the screen recognition feature can identify a lot of what is there, activating said elements, entering text where needed, and just using the app is still a nope. Haven't had the chance to use it on any captchas yet, but could see it working great for things like that.
On my MotoPad, there are a few small bugs. 1. The Braille keyboard doesn't close after text is sent in some apps, even though I have it set to do so in the options. That could be though because the focus is automatically dropped right back in the edit field forcing it to reopen. When using a physical keyboard, the MotoPad has the option to hide any on screen keyboard, but it doesn't with the Talk Forward keyboard, either the regular or Braille keyboard. And, when the keyboard is shown, but I'm not typing with it but instead with the physical keyboard, I get an annoying "end of field" message after every character typed. If I perform the keyboard shortcut for back, it will actually hide the keyboard, but still let me type and not give me that message.
These are things I've already reported, but I get that if there is no access to a given device, it's hard to squash every single bug.
On my Pixel, the Braille keyboard is perfect!
On Samsung phones, it's a bit tricky. My sister has a cheapo A17, and she let me mess around with it. I'm her tech support person. lol Talk Forward will not, as of right now, work propperly on phone startup. This phone is on One UI 8.5. On startup, it tries, will start speaking for a moment, then cuts off, restarts, same thing. Will do that a few times, then just stops. If you know for example that you have to restart the device, you have to turn off Talk Forward, turn on talkback, then restart the phone, enter your pin, then turn on talk Forward and turn off Talkback. It's a lot of work. Once you are in though, and have done all that, Talk Forward breathes new life even in to very budget hardware. I can only imagine how good it would be on an S series phone.
I hope that by the time you get your new phone, this is fixed. The issue is something that has been widely reported, so hopefully a fix will be available soon.
Thanks Justin
Thanks for that summary, Justin. Sounds like TF is doing really well on Pixel devices right now. 😊
As it stands now, I'm waiting for One UI 9 to release. Either the Samsung bug everyone has been reporting will be fixed with that build, or I just won't get a Samsung. The whole reason I wanna pull away from iPhone, is for reasons like App crashes, lag, loss of focus, duplicating text when I dictate, etc, which is currently happening on my iPhone SE 2022 running iOS 18.7.8. I won't even talk about iOS 26 on my backup device... *eye twitch*.
Doesn't make sense to pick up a brand new phone if it's doing the same, or similar, in terms of bugs and performance.
So, either One UI 9 will save the day, or I will just pick up the newest Pixel 11, reportedly coming out on August 20. 🤷
As Of the July 1st 2026 Security Patch For Samsung Devices
, things are a lot smoother and that one issue with Samsung being odd that y'all mention hasn't cropped up on my S23+ as of now.
T-Mobile users got the patch on the 31st of July, not surprisingly.
As for the Screen Rec still being in beta, playing games such as Dice Dreams and Scattered Slots currently can't be done at the moment. Can't wait though for thy feature to be more well-rounded!
Using Prudence for now on the side.
Interestingly (in conjunction with describing the screen), the Visual Aid feature with Dice Dreams (at least ffor rolling the dice), works!
Hi
Hello, after restarting the phone, the TF starts to restart and the password cannot be entered, it says on, off and you need to turn on the talbak. There is also a problem with the speed. It is set to 100% but the real speed is 50-60%.
I also have 3 questions.
Is the support for the TF one-time or monthly?
Is it taken into account for requesting a new feature through the application?
How do I add voices to the rotor because I can't add something?
I use a Samsung S26.
@mantanini
Although I'm not the dev, I shall try and help out best I can.
With that being said, the main question I have for you is:
Which phone are you using?
As for answers:
1. TF support is onetime payment.
2. I'll have someone else answer that one.
3. Adding voices to the rotor can be done from
Talk Forward Settings>Voice>Add A Voice.
Trenton Matthews
I use a Samsung Galaxy S26.
@mantanini
Eeep! Must have missed that detail when first reading your prior post.
In that case,
As Talk Forward 26.8.1 is now available in Google Play, which version are you using? Non-Play Store version or Play Store.
As for TTS speeds when it comes to Samsung, I first wrote that you first have to crank up the normal Text to Speech setting all the way up to 100. (Referring to the system's settings).
But after forgetting that ESPeak has its own Rate settings that's inside its app, you may have to adjust it there.
i get the version of ESPeak NG from
https://github.com/espeak-ng/espeak-ng/releases/download/1.52.0/espeak-1.52.0-signed.apk
, because the ones on the play store (unless that has changed), are either out of date or have ads!
As for voice rates if using the rotor (particularly with ESpeak), choose the DeFault Voice and change its voice via its app.
Changing TTS settings for the rotor (at least for me), I always had to explore by touch to find the rate/pitch setting, double-tapping and holding till I got the speed/pitch right. Up/down swipes on the bar never worked for me for some reason.
Unless that's been fixed now?
I just checked and don't have the july patch yet
S23+ in Canada, hope i get it soon to fix this bug, it hasn't been happening very often for me though so that's good.
Intro Post Updated!
You can now find (under the Getting Started & Support) heading of the main post, links to both the Talk Forward Help Center & Changelog.
What's New with Talk Forward (For the Month of September)
In short, quite a lot!
Version 26.9.3
Released September 20, 2026Android Talk Forward 26.9.3 Offline dictation, with Parakeet • A new dictation engine runs entirely on the device and writes almost as well as the online smart one. Nothing is sent anywhere, it works with no network, it punctuates and capitalizes on its own, and it keeps the English words in the middle of a French sentence. On a Pixel 9, twenty-four seconds of speech come back in a second and a half; the text arrives when you lift your finger. • The model is not in the app: it is downloaded from Settings, Dictation, on the "Parakeet model" row. It is 478 MB, downloads over Wi-Fi only, and takes about 670 MB on the device. Progress is announced, you can leave the screen while it runs, and the same row later deletes it. Speech recognition by NVIDIA Parakeet TDT 0.6B v3 and sherpa-onnx. • Online dictation stays the default engine: it still makes slightly fewer mistakes when you hesitate. Dictation on the device • An "Offline only" engine forces the device's own recognizer instead of letting the system pick a service free to send your voice to a server. A device with no local model says so rather than quietly dictating over the network. • Spoken punctuation is back, and local: say "comma", "period", "new line", and the mark is inserted, with the typography the language wants. The setting is in Dictation and applies to every engine. • A gesture can now edit text by voice: "replace Saturday with Sunday", "delete the last three words", "capitalize Lyon", "read it back", "undo". The command is caught by the device's own recognizer, so it answers instantly, costs nothing and works offline, and every edit says what it changed. An utterance that matches no command changes nothing and is read back to you: it is never inserted into the field. • Numbers spoken in Bengali, Hindi, Tamil, Thai and other scripts are finally understood in those commands. • The Dictation screen is reorganized: the options that belong to the smart engine appear only while that engine is selected. On-screen keyboards • The letter keyboard can show a row of digits above the letters. The option is in the on-screen keyboard settings; the band grows a little taller. • The app now resizes above the keyboard. The send button and the last lines of text used to stay buried under the keys, out of reach until the keyboard was closed. • Spreading two fingers to reach the braille keyboard works at last. The distance it asked for was wider than the screen, so the gesture fell through to the action below it and started a dictation. • That dictation can be stopped again. A two-finger double tap always stops it, where it could start media playback while the microphone stayed open, and locking the phone was the only way out. • No more letter announced twice and followed by "end of field" on every keystroke, with Gboard as with a physical keyboard. And no more double echo in braille in web fields, such as Gmail's compose. Braille keyboard • The dots and the swipes follow how you hold the phone. With the layout setting on "adapt to how you hold the device", the accelerometer decides, live, and a change of posture is announced. An explicit choice, flat or screen away, always wins. Before, anything that was not explicit was treated as flat on a table: anyone holding their phone had the dots and the swipes mirrored, a finger to the left making a space. • Turning the phone half a turn in landscape, charging port on the other side, now turns the dot grid and the swipes with it. Recent apps • The menu no longer goes through a submenu: activating a row opens the app. Pinning and the system app details are now actions on the row, offered by the actions rotor, or by a double tap and hold that opens them as a list. Pinning leaves the menu open; the app details screen closes it first. • The menu remembers thirty apps instead of twelve. • "Previous app" and "next app" are more predictable: the walk is always anchored on the app you are in, so the first gesture always lands on the one used before it. Only apps that can actually be launched enter the list, which keeps permission dialogs and system components out of it. Speech • The time, the battery, the window title, the phonetic spelling and the other announcements you ask for with a gesture are no longer dropped while media is playing, a microphone is open or a call is up. The gesture worked and so did the action: only the sentence was thrown away. Settings • Sound settings no longer crash the reader on a device with no vibrator. The vibration-strength slider added in the previous version depended on a switch those devices do not show. • On a dialer keypad, resting a finger on a key to hear it no longer triggers a long press: "1" no longer calls voicemail and "0" no longer becomes a plus. Typing on lift works, and a deliberate long press is still available by double-tapping and holding. • On a physical keyboard, the arrow keys move from item to item, like a swipe, whatever the rotor is set to. Scripts • A script can declare its own options, with their type and default. They are set in "My scripts", and also straight from the Talk Forward menu of the app the script runs in, so they are not a trip through Settings mid-task. • Scripts get a clock, tf.now(), so they can rate-limit themselves in a chatty app. Help and translations • The help finally describes the gestures that are actually in force. Sending from the braille keyboard is three fingers up, not two; hold to dictate is off by default; the scrub needs a single back-and-forth; the rotor has its groups; the two-finger swipes list their real defaults; and a section describes the letter keyboard. • The braille keyboard gestures page describes the keyboard you actually type on, and the gestures you customize there finally apply. • Every string is translated into the app's 75 languages: about twenty thousand texts were still showing in English. In Simplified Chinese, the dictation engine list could show the wrong engine.
Version 26.9.2
Released September 14, 2026Android Talk Forward 26.9.2 Recent apps • Talk Forward now keeps its own list of recently used apps, with three assignable actions built on it. "Previous app" and "next app" walk the list Alt-Tab style: swipes chain together, and the app you stop on becomes the most recent. "Recent apps" opens the list as an ordinary Talk Forward menu — explorable by touch, navigable by swipe, closed by Back, spoken in the reader's own voice. Each app there offers open, pin or unpin, and its system app-info screen. A pinned app heads the list whether or not it has been used lately. No gesture is bound by default: the three actions are waiting at the bottom of the action list. • The list is observed, never queried: an app enters it after staying in the foreground for about a second, which keeps out transient activities, share sheets and permission dialogs. Home screens, the system UI, the active keyboard and Talk Forward itself never enter it. It survives a restart. Actions inside an app • A gesture can now do something in an app rather than merely open it: call a particular contact, open a particular conversation, start a route. Pick "Action in an app" from a gesture's action list: Talk Forward lists the apps that can build one, and it is the app's own chooser that opens to let you pick the contact or the conversation. Nothing about its interface is guessed, so nothing breaks when it is updated. Coverage depends on the apps: on a Pixel, Contacts, WhatsApp, Maps, Gmail, Docs and Settings all offer one. • Fixed along the way: in the per-app gesture editor, choosing "Launch application" stored a gesture that did nothing. Vibration • A slider sets how strong every vibration of the reader is, from a quarter to double its normal strength. It sits in Sound and vibration, under the vibration switch. On a device whose vibrator cannot vary its strength, the patterns play as authored rather than pretending. • On-screen braille typing finally vibrates, as the letter keyboard already did. Both keyboards share one setting, renamed "Typing vibration". Braille cells get the lighter tick: a cell lands far more often than a key. Physical keyboard • Ctrl, Alt and the Windows key can now serve as the Talk Forward modifier, alongside CapsLock, Insert and Scroll Lock. Left and right stay separate choices, so binding one leaves the other doing its usual job. Note that pressing Ctrl interrupts speech, a behaviour independent of keymaps, and that Android reserves some Windows-key combinations for itself. Explore by touch • The finger and the swipe select the same thing again. On a rich row — a message in the Gmail widget, a notification — exploring by touch selected a fragment of the row, its sender or its subject, where a swipe selected the whole row. The next swipe then carried on from the fragment. • The finger no longer falls into holes. A widget's margins and the few pixels between two rows belong to the container: crossing them cut the message being read to announce "Gmail", over and over. Those areas are now treated as a hole in the item being read, not as a new item. • An announcement is no longer cut off by the hover that follows it on the same item. In the notification shade a notification would start being read and be interrupted thirty milliseconds later by another hover on that same row: nothing was ever heard. • On a screen-filling backdrop — the home screen page under the icons — the description is no longer repeated every time the finger lands back on empty space. It is spoken on arrival, then when it changes, which is when you change page. In between, a regular tick tells you the finger is on empty space. Braille • Correcting a word mid-typing no longer strands the start of the word in the field. Deleting a cell and retyping produced "dedernières" instead of "dernières", because the deletion committed what was being composed. Ringer • The rotor now tells the truth about silent mode: on Android an app can only reach it by turning Do Not Disturb on. The announcement says so instead of implying plain silence.
Version 26.9.1
Released September 12, 2026Android Talk Forward 26.9.1 Visual agent • The agent now answers follow-up questions. When it has finished speaking, the microphone stays open for five seconds: carry on without touching anything. "Tell me more about that button", "and just below it?", "press it" — your previous question and its answer go with the new one, so it knows what you are referring to. Say nothing and the window closes silently: no beep, no prompt to sit through when the answer was all you wanted. The five seconds are counted from the moment the microphone opens, not from the start of the answer, so a long description never eats into your time to speak. • The agent also performs the Talk Forward actions you name. "Next item", "home", "turn screen recognition on" — everything you can assign to a gesture is recognised by its name, in your language, without going through our servers. The matching is deliberately strict so that it never confiscates your questions: "what is the next button?" is still a question for the agent. Sound • The screen reader volume can follow the media volume, and the other way round. The option is in Sound and vibration, under the volume slider. With it on, moving either one moves the other, whether you use the volume keys, the slider in the settings, or Android's own audio settings. The two do not have the same number of steps, so it is the relative level that is matched. On-screen keyboards • A two-finger scrub closes the keyboards. The gesture that means "back" elsewhere now works on the letter keyboard band as well, and during braille input, where it closes for good: no other keyboard takes its place. • Letter keyboard: what you touch and what your swipes act on can no longer drift apart. After exploring an element of the app above the keyboard, a swipe right still announced the next key. The keyboard and the screen reader now share a single cursor: exploring a key brings it onto the keyboard, exploring or reaching an element of the app brings it onto the app, and a swipe acts on whichever of the two you are actually on — whether the gesture is made on the keys or above them. A new setting, in the on-screen keyboard preferences, decides where the cursor starts when the keyboard opens. • Braille input: in number mode, a cell is no longer announced twice under two names. The number prefix followed by dots 1-6 said both "1" and "a circumflex". The keyboard's announcement now asks the edit buffer what the cell will actually write in its context, instead of translating the cell on its own. Capitals benefit too: the capital prefix followed by a letter announces the capital. • Braille input: no more "end of field" after every cell you type. Each insertion makes the field report that the cursor moved, and the screen reader announced that move on top of the keyboard's own echo. Cursor moves you ask for are of course still announced. • Braille input: browsing autofill suggestions no longer sticks. Once opened on an address or password field, it survived the keyboard closing, and every later session started inside it — swipes up and down cycled suggestions instead of moving the cursor, with nothing to say why. It now closes with the keyboard, and typing a cell leaves it. Calls • The caller's name can be repeated for as long as the phone rings. A single announcement gives you a single chance: the ringtone starts at the same moment, or you are not next to the phone, and the only way left to find out who is calling is to pick it up. You choose what is announced — the name, the number, or both — and how often it comes back. • Answering and hanging up now work for calls from messaging apps, with the two-finger double tap. A Telegram or WhatsApp call is not a phone call as far as Android is concerned: the system saw it ring and then lost sight of it, and the instruction to answer was lost with it. Talk Forward now presses the button on the app's own call notification, exactly as you would, and only turns to the system afterwards. Touch exploration • No more items that vibrate and play their sound without saying anything. It happened a great deal in the notification shade, but also on a widget or in a web page, and never when swiping. Two separate causes: an item that already held the focus was not announced at all when the finger arrived on it, and an expanded group — a notification you have opened up, for instance — swallowed everything inside it, so the finger could travel over several texts without the cursor ever moving. Inside an item that has already been announced, exploration now goes down to what is really under your finger. Play and pause • The two-finger double tap finally works everywhere. It did not pause Prime Video and did not answer on WhatsApp, while a button on a wired remote did both. Talk Forward now drives whatever is playing directly, the way the buttons on the player's notification do, and falls back to a real media key when there is nothing to drive. For calls, the "answer" key of hands-free kits is sent first; if the call has not moved a moment later, the precise routes take over. Rotor • The rotor says when it has nothing to offer. Turning it with no reading control available made no sound at all, which is indistinguishable from a gesture that was not recognised, from a broken feature, and from a screen reader gone mute. Dictation • The field's placeholder no longer ends up in front of your text. Dictating into an empty message field inserted "Message hello, what time…". Apps that show that prompt text without declaring it as such are now recognised, and the field is treated as empty. Translations • The text added by this version is translated into the 28 languages Talk Forward already covers.
Talk Forward Companion (MacOS)
The fact that this was originally released all the way back in June and no one has brought it up till now (which you can check out it's changelog here , is actually quite shocking!
Download can be found via the main Talk Forward site by navigating to the "Desktop companion" heading (which is at level 3).
Re: What's New with Talk Forward (For the Month of September)
Damn. I cannot wait to get my hands on an Android device.
Re: Talk Forward Companion (MacOS)
Thanks Trenton, unfortunately that page will not load for me. 🙁
Re: Talk Forward Companion (MacOS)
You know? I forgot that there was a "reply" link....
Anyway, visiting
https://app-suite.eu/talkforward
, is not having issues over here on my end.
Tried both Edge & Chrome (in regular & private tabs).
You may have caught yourself in that cookie notice thing. Either accept it or Jump to the top of the page first.
Even downloading the Companion app on my Windows machine works! Won't do anything for me obviously but wanted to make sure there weren't issues downloading it.
Could someone please compare it to Voiceover on iPhone?
Hey there! Great work! I don’t have an Android and am not considering getting one any time soon, but I’m really wondering how the responsiveness of Talk Forward compares to Voiceover? I made an attempt to switch to Android back in 2022 and even got a flagship Samsung…. But gosh, whatever screenreader I used, it never got as fast as Voiceover on iPhone 4 :)
Don’t even get me started on Apple Watch Serious 2 vs the latest Samsung and other watches! But it’s a different story though
Re: Could someone please compare it to Voiceover on iPhone?
Hi Eyesfreesight,
It's probably best to create a new Forum Topic to ask this question, because Android-to-iOS comparisons tend to draw ... a lot ... of opinions, and those types of discussions can quickly become very, very involved and go in a lot of different directions. I recommend keeping this particular topic related to Talk Forward only.
Re: Could someone please compare it to Voiceover on iPhone?
Totally agree with Michael 's thoughts on the matter here.
Definitely mention (in a separate thread/topic) "Talk Forward" in the subject line, for anyone wishing to compare the two.
Talk forward dictation
Hey, so I'm a bit confused here. So if I double tap with two fingers on the screen when I'm in a text field, would that activate a Dictation service of my choice that I have selected in the Dictation settings of talk forward? I'm running an Opo find X5 light running android 13. I know for talkback when I double tap with two fingers when I'm in a text field. It uses the normal Google voice typing thing pre-Google Pixel six which is no punctuation at all, so I don't usually use it.
Re: Talk forward dictation
Correct.
Though you have to make sure it set up beforehand.
E.G., your Google Gemini API key is added first before use.
Otherwise, the two-finger double-tap defaults to the normal Google Voice typing.
FYI: If using GBoard, you may need to turn off Voice Input since Talk Forward has its own version.
Re: Talk forward dictation
how good is the dictation with Google Gemini?
Re: Talk forward dictation
If you're referring to Gemini's Smart Dictation, "EXTREMELY" good! Yes, I put extremely in all caps. It's that good!
You know that Rambler feature that Pixels have had for a little while with GBoard? Talk Forward has it built-in, and can be used with any keyboard!
Not just Talk Forward or GBoard's own keyboards.
TalkForward sounds amazing
I truly cannot wait to get my hands on an Android device so I can play around with TF. 😇
Great but one major bug
I'm super happy with TF for the most part, but there is one major issue I've experienced with the upgrade to 26.9.3, where in the Braille keyboard, all my letters type normally, but then sometimes my swipes are all wrong, like instead of swiping right to space, it deletes a letter when I swipe right and I have to swipe left instead. What's even more frustrating is that it can happen to me mid message. Can start out working just fine, then suddenly, it isn't. No rhyme or reason. I always use screen away mode on my Pixel. Haven't experienced it on my MotoPad, but I've been using that with the phyysical keyboard a lot more lately, so it could be a thing there, I just don't know.