Hi All,
This will be a very long, and detailed post. However, I want to bring as much information to this as I can in one place, so that we can hopefully figure out a way forward and a practical solution, either temporary or permanent.
As many of you probably know, FlickType was an incredible keyboard app for IOS, specifically developed for blind and low vision users. For me and many others, it was a revolutionary typing experience that was like nothing I've seen before or since, on any touch screen keyboard. The basic concept as described on the FlickType Website is, "Delete and change entire words with a single flick of your finger. Control the cursor directly from the keyboard. When typing, don't slow down and try to be accurate. Simply tap-type where it feels right and FlickType's unique algorithm will find the correct word from the pattern of your taps." In other words,
- based on where you think the letters should be on the screen, type the word you want, and swipe right. FlickType will guess the word you wanted based on your finger positions and it's algorithms etc.
- If it chooses the correct word, just keep typing/swiping and repeat the process. If not, swipe down to hear more suggestions for the word you entered, and when you find the right one, keep typing the rest of the phrase. When you're done, swipe right again to enter punctuation. (period, comma, etc.)
This is very hard to explain effectively in writing, but it's incredibly easy and intuitive when you actually use the keyboard. It's auto-correction and suggestions were impressively accurate, and I used it as my primary system-wide keyboard for at least 3 or 4 years, that's how good it was. It even had ways to add names/custom words that it didn't know by default, so it would recognize them when you typed them, and a whole bunch of other very helpful features.
A Little History:
FlickType was developed by Kosta Eleftheriou and his wife Ashley. The app was originally developed as Fleksy, before he later sold Fleksy to Pinterest, when they promised that the keyboard would remain accessible to blind and visually impaired users, and then promptly broke that promise just months after their acquisition. Here's an old article on the merger.
Then, 2 years later, Kosta launched FlickType, which brought back Fleksy's original keyboard technology with some new features, and a much-appreciated system-wide keyboard extension. An NFB article from 2018 summarizes all of this as well.
Then again, about 2 years later, Apple's fight with Kosta begins.
Kosta's first issues with Apple began in late 2019 into 2020, when Apple started taking his app off, and then back on the app store, for no clear reason. You can read Kosta's account of what happened here. Eventually, Flicktype was back on the app store and all was good...until scammers started copycatting Flicktype as a "shell app" and charging users subscription fees for an app that never worked. Kosta documents this at great length here, and you can read more about the ridiculous amount of app store scams in this Verge article as well. Despite numerous press stories and direct inquiries to Apple from journalists, the scams still continue to this day, and Kosta, understandably so, couldn't take it anymore.
In 2021, Kosta wrote: "It's with a heavy heart today that we're announcing the discontinuation of our award-winning iPhone keyboard for blind users. Apple has thrown us obstacle after obstacle for years while we try to provide an app to improve people's lives, and we can no longer endure their abuse."
Discontinuing the Extension
After making this announcement, Kosta stated he would leave the FlickType app on the app store, for both iPhone and watch, but he would discontinue the system-wide keyboard extension. This drew quite a bit of backlash, and in my opinion, some rather unwarranted vulgar comments directed to Kosta online by some of the blind community. Of course I shared the frustration at the extension being gone, but screaming expletives at the developer certainly wasn't going to make him change his mind ;)
A few months later, I sent an email to Kosta. I'm also a registered developer with Apple, and while I have no experience developing an app at his level, I at least wanted to reach out and lend a helping hand if I could. I asked him what his future plans were, if I could be of any assistance etc, with no response.
Then in late 2022 I messaged him again, this time on X (formerly Twitter). It really hit me hard when FlickType's keyboard extension stopped working, because I almost had to relearn how to type on the regular IOS keyboard, because I had used FlickType regularly for so long. I was starting to really want to figure out a way to bring the app/keyboard back and thought maybe he hadn't seen my email. But again, no response.
Where are we Now?
FlickType version 2021.8 was the last version in the app store to contain the keyboard system-wide extension. It is still in the app store as of this writing, with a 2024 bug fix update. However, it seems to be almost entirely focused on the watch keyboard side of the app, and the iPhone "container" form of the keyboard long forgotten. VoiceOver with IOS 17 kind of works the way FlickType was originally intended, but words don't read out properly after you swipe right, and there are a number of other inconsistencies, likely caused by Apple's OS update but still unresolved. Again, I reached out to Kosta on X with no response yet as of this writing; I'll update here if that changes.
I did find that someone posted an IPA file of FlickType just before the extension vanished, but the file is still encrypted, so trying to install it on your iPhone yields numerous errors. And even if you were able to get it installed, I have a feeling it would suffer from the same bugs of the current app store version as mentioned above, due to changes in IOS updates.
My goal here is not to "out" this developer, or even Apple for that matter, though I think they absolutely have some explaining/cleaning up to do. But especially if FlickType's legal battles seem to be over, there has to be a way for blind and visually impaired users to have access to this typing experience that was so amazing. Whether that's making something open-source through Github or similar platforms, using Test Flight, or maybe even using a third-party app store if they come to the US, given the recent changes to app store controls and payment processing etc due to European laws. I know Apple is still creating loopholes around these changes which Kosta has also recently highlighted, but I'm just throwing it out there as a possible suggestion. No one should ever have to endure what Kosta has gone through in the past few years. But let's at least start the conversation. and figure out a way to continue to pursue transparency and accountability from both developers and giant tech companies, while simultaneously allowing life-changing apps to prosper. Let's bring the full FlickType experience back for good.
Comments
Definitely supportive
I was also a user of the app and, for me, it was definitely life-changing. When you consider how much a blind person in modern times leverages his or her smart phone to compensate for poor accessibility and his or her environment, having a reliable and productive Keyboard is it true quality of life upgrade.
I am not a developer, but I would like to support any efforts I can to bring this application back. Thanks for starting the thread!
Testflight
Arn't their limited slots you can have on testflight though? However, I quite like this idea of bringing it back.
I do too!
Hello,
I love what FlickType did & miss it.
I, too wish it could be resurrected.
Good concept
First, let's be clear that the shaking out isn't just between US and EU: the United Kingdom is no longer a part of the EU and since the assimilation of retained EU law by virtue of the Retained EU Law Amendment and Revocation act 2023 such rules formerly held in common with the EU are either no longer in force or amendable in the normal way. whether or not anyone wishes the UK were still in the EU, it isn't. Our own data regime is likely to look very different as a consequence in the near future, likewise our own standards applicable to the trading of intellectual property such as software.
Now, to Flicktype: when Costa brought this back and wrote about it on the AppStore, or rather, when he was proposing doing so, he asked former users to give him feedback on whether they would come back to it. I was very honest. Since BSI, said I, I would not go back to Flicktype as BSI works very well for me indeed, to the extent that if I were to buy another iPad I wouldn't bother with a keyboard folio for it. But prior to BSI, I thought the Flicktype concept was a genuine game-changer. For those of you who depend on that type of keyboard, I really see why you need it back for your productivity. So while I have no direct interest in this project, i wish it all the best. I do agree with Oliver that the Voiceover support broke long before the app discontinued. this was noticeable when I used it on the watch, particularly with apps like Chirp for twitter.
Re: Good concept
Agree. Ever since I started to use BSI, I never used flicktype as my primary. however, that didn't despise the concept and still thought it was pretty neat and still played with it at times when it was still around however with that being said, I relied on BSI a lot more honestly. I do see the need for it to some people and if it was back, I wouldn't be opposed and it would be fantastic if it were.
A really great keyboard
The Fleksy experience was really superb and one of a kind for blind users. I'm guessing that it was also very useful to sighted people.
It was a tragedy to see it go away, especially how it happened. Kosta's heart genuinely seemed to be in the right place, but some battles just aren't worth fighting and sometimes one just has to move on.
I am a bit surprised that Apple didn't just buy him out and take on the job of supporting and further developing the app. As I said, I think it not only benefited blind people, but also benefited sighted folks. In either case, the keyboard would offer some choice for all users and choice is generally a good thing.
--Pete
Does the keyboard still work on the apple watch?
I can’t find a clear answer. I’ve downloaded the app to my phone and watch (iphone 14+ and an apple watch series 6) both on the latest software) but every time i open it on my watch it just says open app on iphone to unlock even though its open on my phone as well and does nothing. Am I supposed to buy the app to be able to use it? is it even still active? Because I don’t want to pay for a dead app. Also if I can use it is there a way to access dictation from the keyboard?
Great experiences with a few flaws
I quite liked the app for what it was and at the time it was released it most certainly was a leap forward in accessible typing. I never could use the app to it's fullest potential though given that until it went down it only supported English and spanish as input languages. While there were multiple users asking for more languages to be supported, it was always stated that this would be to much work. So while the app was awesome it really lacked potential and a bigger user base.
Personally I sticked to direct touch typing that was introduced in iOS 8 and while it might be difficult for some to learn, I am matching flicktype speeds and am not bound to a certain language.
So while I would support a return of the app, unles more languages get supported I don't see myself going back to it.
I've never understood how…
I've never understood how some totally blind folks have managed to master direct touch typing on iPhone.
Direct touch typing
Yeah I really like direct touch typing too and can type pretty quickly.
The main advantage that FlickType had over it though was that keys like Shift, Delete, Return and Spacebar were not on the screen and those actions were done with gestures instead. With direct touch typing I do find I tap those keys when I’m aiming for a letter.
Dave
Same.
A new version of flicktype would be awesome!
Agreed
Yes, I agree completely!
I loved the app & miss having it around.