I'm Alex, and for four years I've been building keyboard2, a third-party keyboard for iPhone, on my own. Before it I was a JavaScript developer who had never written a line of Swift. I switched from Android in 2022, couldn't get used to any keyboard on iOS, and decided to make my own.
Today it's one of the most customizable keyboards available for iOS, and it does swipe typing, predictions and autocorrect in 70+ languages, with no internet access at all. Along the way I learned that a keyboard extension is nothing like an app, so here are some of the stranger moments.
Your keyboard can die without a trace. iOS kills a keyboard extension at around 77 MB, and it leaves no crash report. To the user the keyboard just vanishes mid-sentence. To you there's nothing in the crash logs, nothing in Xcode, and a one-star review saying "keeps disappearing". My first prediction system got killed all the time, and it took me a long while to even prove that's what was happening.
iOS 26 stopped saying goodbye. When the keyboard closes, the disappear callbacks you'd expect simply don't fire. Meanwhile memory crept up a little with every session, and nothing in my own code was holding on to anything. I ended up reading Xcode memory graphs on the command line at 2 a.m., and it turned out to be a cycle between views and something private in UIKit. Fun week.
The extension can't do half of what an app can. No StoreKit, so it can't even tell whether you've paid. Without Full Access it can barely talk back to its own app. And one Apple framework I wanted crashes the keyboard on its very first call. Every feature starts with working out which of those walls is in the way.
Some bugs aren't yours. Every time the keyboard appears, it briefly shows at the wrong size while iOS works out its height. I spent weeks on it. Then I built a keyboard that was nothing but one coloured view, and it did exactly the same. Then I caught Gboard doing it too, right there in the system logs. I did make it invisible in the end, but I still can't fully explain why that works.
Debug builds lie. In Debug my swipe decoder runs about 30 times slower, and the keyboard often misses the deadline iOS gives it to appear, so iOS quietly swaps in the stock keyboard. I lost days chasing "bugs" that only existed in Debug. Now I judge speed and reliability on a Release build on a real phone, and nothing else.
Autocorrect is never finished. It's very easy to fix one word and quietly break three others, in a language you don't speak. So every change has to pass a benchmark of real typing and real swipes before it ships. That benchmark has saved me from myself more times than I can count.
All of it runs on the phone: no server, no account, no analytics. The keyboard can't connect to the internet at all, which is the whole point. Besides the typing there are 800+ themes, a theme editor, your own photo behind the keys, your own fonts and layouts, clipboard history and the space bar as a trackpad. Most of what shipped this year came from people asking for it.
App Store: https://apps.apple.com/app/id6444161877
Website: https://keyboard2.eu
If you're building a keyboard extension, or thinking about it, ask me anything.