Skip to content → Skip to footer

From TalkBack to Jieshuo, and Now SandFly: My Journey Through Android Screen Readers

After years of using TalkBack and Jieshuo, I’ve decided to make SandFly my primary screen reader.

For me, this isn’t simply about replacing one application with another. It’s also an opportunity to look back at how Android accessibility has evolved over the years, what we’ve gained along the way, and what I expect from a screen reader today.

I’ve been using Android for a long time, and I’ve witnessed quite a few changes in its accessibility ecosystem. Some were genuinely exciting, while others reminded us how limited our choices were.

2013–2020: The Years of TalkBack

For much of the period between 2013 and 2020, TalkBack was practically the only realistic option for many blind Android users.

There were other attempts and alternatives, of course, but TalkBack dominated the ecosystem. It came with Google’s backing, was integrated into Android, and worked across a wide range of devices.

I don’t want to underestimate what TalkBack meant to us during those years. It made Android usable for millions of blind people, including me. It improved considerably over time, and many features we take for granted today were not available in its earlier versions.

However, there was always something that bothered me: performance.

TalkBack often felt heavier and slower than it needed to be. Navigating through interfaces, moving between elements, and performing everyday tasks sometimes required more patience than I thought was reasonable.

And when you use a screen reader for practically everything you do on your phone, these small delays add up.

The problem wasn’t simply that TalkBack was slow. It was that we had very little choice. If something didn’t work the way we wanted, we could report it, wait for an update, or learn to live with it.

For years, that was simply the reality of Android accessibility.

2020–2026: Jieshuo Changed My Expectations

My experience with Jieshuo changed the way I thought about screen readers.

For the first time, I felt that I was getting much closer to the full performance of my Android device.

The difference wasn’t limited to speech responsiveness. Navigation felt faster, interactions were more immediate, and I had considerably more control over how my screen reader behaved.

Jieshuo offered a level of customization that TalkBack had never really provided. I could adjust the experience to suit my habits rather than constantly adapting my habits to the screen reader.

Once you become accustomed to that level of responsiveness and flexibility, going back isn’t easy.

But Jieshuo had its own problems.

One of the biggest challenges was communication with its developer. When something didn’t work properly, reporting an issue and getting meaningful feedback wasn’t always straightforward. For a product that plays such an important role in our daily lives, communication matters enormously.

There was also the issue of distribution and compatibility.

Because Jieshuo wasn’t available through Google Play, certain banking applications and other security-sensitive services occasionally created problems. Some applications treated the screen reader as a potential security risk, even though we were simply using it to access our devices.

As a blind user, I found that particularly frustrating.

A screen reader isn’t an optional convenience. It’s the interface through which we interact with our phones. Having to choose between using the screen reader I prefer and accessing essential services is not a reasonable situation.

And then there were the practical complications. Even something as ordinary as paying for a screen reader could involve additional services, intermediaries, or procedures that an average user shouldn’t have to deal with.

These things might seem relatively minor when considered separately, but together they affect the overall experience.

Jieshuo showed me what was possible in terms of performance and customization. At the same time, it made me appreciate certain advantages I had previously taken for granted.

TalkBack Was Always My Safe Harbor

Despite all my criticism of TalkBack’s performance, I never completely abandoned it.

There was something reassuring about knowing it was there.

TalkBack was officially supported, widely recognized, and generally less likely to create complications with applications that were sensitive to accessibility services.

Whenever I encountered a problem with Jieshuo, I knew I could return to TalkBack.

It might not have been as fast or as flexible as I wanted, but it provided a familiar and relatively predictable experience.

In that sense, TalkBack became my safe harbor.

And I think that says something important about screen readers. Performance matters, but so do stability, reliability, compatibility, and trust.

The ideal screen reader shouldn’t force us to sacrifice one for another.

What Should We Expect From an Android Screen Reader?

After all these years, I think we need to reconsider what we actually expect from an Android screen reader.

Of course, responsiveness and advanced features matter. Nobody wants to use a slow or unnecessarily restrictive screen reader.

But speed alone isn’t enough.

A screen reader should be stable, reliable, and inclusive. It should be easy to obtain, straightforward to set up, and accessible to people with different levels of technical experience.

You shouldn’t need a master’s degree, let alone a PhD in technology, just to configure your screen reader and use your phone comfortably.

I enjoy experimenting with technology. I don’t mind exploring advanced settings, testing new features, or finding workarounds when something doesn’t behave as expected.

But that’s my personal interest. It shouldn’t be a requirement for everyone else.

Someone who has just started using Android with a screen reader should be able to learn the basics without feeling overwhelmed. Meanwhile, experienced users should have access to the advanced tools and customization they need.

These two expectations aren’t contradictory.

A well-designed screen reader should be approachable for beginners without becoming restrictive for advanced users.

Accessibility must extend beyond the application’s interface, too. Installation, updates, payments, documentation, and communication with developers are all part of the experience.

If obtaining or paying for an accessibility tool requires navigating through several third-party services and complicated procedures, then something is wrong with that experience.

These considerations have become increasingly important to me, and they’re among the reasons I’ve started looking at SandFly more seriously.

SandFly: A Familiar Foundation With New Possibilities

What initially attracted me to SandFly was its approach.

Because SandFly builds on TalkBack’s foundation, many aspects of the experience already feel familiar. Its settings, menus, and general structure don’t require me to forget years of accumulated habits and start from scratch.

That’s a significant advantage.

Changing screen readers isn’t always easy, particularly when you’ve spent years developing your own gestures, routines, and ways of interacting with Android.

With SandFly, I feel that I’m getting something close to the safety and familiarity of TalkBack, combined with a much more capable and comfortable environment.

If TalkBack was my safe harbor, SandFly feels like that same harbor opening into a much more luxurious bay.

It’s a slightly unusual comparison, perhaps, but it describes the feeling quite well.

The familiar foundation is still there, while the possibilities continue to expand.

SandFly is still a developing project, and I don’t want to pretend that every feature is perfect or that it has already solved every problem. However, its advanced capabilities are progressing, and I’ve been encouraged by the direction of its development.

Another important advantage is how approachable the experience feels.

I don’t have to spend hours trying to understand an entirely unfamiliar system just to configure the basics. At the same time, there are more advanced possibilities to explore as I become accustomed to it.

That balance is exactly what I want from a modern screen reader.

The Practical Details Matter

There are also some very practical reasons behind my decision.

First, paying for the software doesn’t have to become a separate technical challenge. If I decide to purchase it, I don’t have to deal with numerous intermediary services just to complete the process.

That might not sound particularly exciting, but simplicity matters.

Second, SandFly hasn’t caused problems with the banking service I personally use.

I want to be careful about how I describe this. My experience doesn’t mean every banking application will necessarily work without issues for every user. But for me, being able to use my preferred screen reader without compromising access to an essential financial service is a major advantage.

And then there’s something that deserves more attention: physical keyboards.

SandFly appears to place considerable importance on physical keyboard support, and it’s clear that thought has gone into this part of the experience.

This matters to me personally because I don’t use Android exclusively on a phone. I also use a tablet, and physical keyboard interaction is an important part of how I work with it.

A screen reader that treats physical keyboard navigation as a serious part of the user experience, rather than an afterthought, immediately becomes more interesting to me.

I don’t think physical keyboard support receives enough attention in discussions about Android accessibility.

We often focus on touch gestures, speech responsiveness, and customization. Those are important, of course, but Android is no longer limited to the traditional smartphone experience.

Tablets, foldables, keyboards, and different ways of interacting with our devices deserve equal consideration.

The more I explored SandFly from this perspective, the more I began to feel that it could become a screen reader I would genuinely enjoy using every day.

Communication Is Part of Accessibility

There’s another factor that has influenced my decision: communication with the developer.

After my experience with Jieshuo, I have come to value this much more than I used to.

Being able to contact a developer, explain a problem, discuss an idea, and receive feedback makes a real difference.

This doesn’t mean every suggestion should be accepted or every bug should be fixed immediately. Software development doesn’t work that way.

What matters is knowing that communication is possible and that users’ experiences are being considered.

Through my work with Accessible Android, I’ve spent a considerable amount of time testing applications, reporting accessibility issues, and communicating with developers.

One thing I’ve learned is that the relationship between developers and users can influence the quality of a product just as much as technical decisions do.

SandFly’s developer has been approachable, and that gives me another reason to follow the project closely.

Of course, good communication alone doesn’t guarantee good software. The product still has to demonstrate its reliability through daily use.

But when a project combines technical ambition with an approachable developer, I’m much more willing to invest my time in it.

A New Chapter, Not a Final Verdict

I’m not switching to SandFly because I believe TalkBack has become irrelevant or because I want to dismiss everything Jieshuo has offered me.

Quite the opposite.

I appreciate what both screen readers have contributed to my Android experience.

Without TalkBack, my early years on Android would have been very different. Without Jieshuo, I might never have realized how much faster and more flexible screen reading could feel.

But I’m also not particularly interested in remaining loyal to a screen reader simply because I’ve used it for years.

My loyalty is to accessibility, independence, and the freedom to use technology in the way that suits me best.

SandFly will have to prove itself through everyday use. There will almost certainly be bugs, missing features, and situations where I may need to return to another screen reader.

That’s perfectly normal for a developing project.

For now, however, I see enough potential to make the transition.

What I find particularly encouraging is that we seem to be moving toward a more diverse Android accessibility ecosystem.

We no longer have to evaluate screen readers solely in terms of whether they can read an interface. We can discuss performance, usability, reliability, physical keyboard support, distribution, payment accessibility, developer communication, and the overall quality of the experience.

And we should.

After all, an Android screen reader shouldn’t simply make a device accessible.

It should make using that device comfortable, efficient, and enjoyable.

That’s what I’m looking for in SandFly, and that’s why I’ve decided to give it a chance.

About Author

Salih Kunduz

Salih Kunduz is a co-founder of Accessible Android and has been using Android since 2013. His work focuses on Android accessibility, screen readers, apps and devices, with a particular interest in how accessibility works in real-world use. Over the years, he has worked with developers and accessibility communities to identify barriers, test improvements, and help make Android apps and services more accessible. He also writes reviews, guides, and in-depth articles on Android devices, apps, and accessibility developments.

Published in Articles

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

Donate to Us

To uphold the standards of a robust and fully accessible project, we graciously request your support. Even a modest contribution can have a profound impact, enabling Accessible Android to continue its growth and development.

Donations can be made via PayPal.

For alternative methods, please do not hesitate to contact us.

We deeply appreciate your generosity and commitment to our cause.

Subscribe to Blind Android Users mailing list

RSS feed: Accessible Android on Mastodon Accessible Android on Mastodon

  • Untitled
    From TalkBack to Jieshuo, and Now SandFly: My Journey Through Android Screen Readers https://accessibleandroid.com/from-talkback-to-jieshuo-and-now-sandfly-my-journey-through-android-screen-readers/
  • Untitled
    New app added to Accessible Android apps directory: Twangle: Guitar Tuner accessible https://accessibleandroid.com/app/twangle-guitar-tuner/
  • Untitled
    New game added to Accessible Android apps directory: PLOT: AI Interactive Fiction accessible https://accessibleandroid.com/app/plot-ai-interactive-fiction/
  • Untitled
    New app added to Accessible Android apps directory: AcessGallery accessible https://accessibleandroid.com/app/acessgallery/