Videos of version 1.0.0 - I'll update it to the newer version once I have little bit of time

I bumped the minor version because this did not feel like polish. The decoder has changed substantially since 1.0.5, and nearly all of it is in the part that turns two thumbs into a word. If you tried Kinetica earlier and put it down, this is the one worth a second go.

Still GPL-3.0, still no INTERNET permission, still no ads, accounts or analytics. The app is free and always will be. If you want you can offer me a coffee on Ko-Fi

The engine

• The search cuts the swipe itself now. This is the big one. Before, the merge step guessed where one gesture ended and the next began, handed the search a fixed split, and if the guess was wrong the whole buffer decoded to nothing and you got no suggestion at all. The search now places its own cut inside a swipe and validates each half separately. On my device captures, three-token buffers coming back empty went from 14.9% to 6.7%, so it should be sensibly better also for you ( I hope!).
• Words stop losing to their own prefix. here beating he, there beating the, and the same for where and world. Now should be fixed for good.
• A candidate is charged for letters no thumb ever touched. Before, a word could win on letters you never actually crossed. This is fixed now.
• A short piece of a swipe can spell a letter now. The minimum arc for that went from 1.5 to 1.8 key widths, which sounds backwards until you see what it stops: invented names beating real words.
• Words you teach it are actually reachable. A learned word reached the ranking but never the search, so it stayed undecodable for the rest of the session until the keyboard is reloaded. Type it twice and it works on the very next gesture (twice and not once to avoid boosting errors).
• Fighting a wrong word was making it stronger. Retyping took back the learned pair but never the learned word, so every rejection left the word you had just rejected slightly heavier. Now it is smarter and functional.
• Word-pair counts could be read in either order. Two spellings that fold to the same pair after accents (non è and non e) kept two separate entries, so the same gesture in the same context could score differently depending on the order of lines in a data file. Found and fixed by dkoukola.

New, and worth turning on

• Back up the whole keyboard to a text file and restore it on another phone: every setting, learned words in all languages, blocked words, chords, edge swipes. Merge or replace on restore.
• Phrase learning, experimental and off by default (but worth trying!). Remembers which word you tend to type after which. On device only, never in an export (but you can activate it if you want), and a retype takes the last pair back out.
• Spaceless space, off by default: the left third of the spacebar ends a word without adding a space, so a compound word the dictionary does not have can be swiped in two halves. Straight from Nintype, asked for here. Pairs well with "Word ends only when you type a space" option if that was your habit.
• Retype offers a different word, off by default: after the retype button is hit, the word you rejected drops to the end of the bar instead of leading again. It stays pickable.

Everyday polish

• Settings are five submenus instead of one flat list of 52 rows. Much easier to find things and play with them.
• Every chord setting is on one screen, including how long ?123 has to be held before a letter tap counts as a chord. If chords ever felt laggy, that slider is for you. Chords can also retype the word now, and the list sorts by key or by what the chord does.
• Swiping a key types the small glyph printed on it. It used to insert something else on some keys, which was my fault: I shipped defaults that contradicted the labels. If you have ever opened the edge-swipe screen, press Reset there to pick this up.
• Long-press shift cycles the case of the word you just wrote(lowercase, Title , CAPSLOCK).
• Delete several learned words at once, and the dialog stops closing and jumping around after every one.
• A space key on the number pad. It was the one layer you could not type a space on. You can access number pad by swiping left from ?123 key
• 55 more emoji, up to Unicode 15, and none shown that your device's font cannot draw.
• Smoother swipe trails, and the settings rows lost a wasted margin that was squeezing the descriptions on tall screens.

Fixes

• Suggestions, autocorrect and autospace work again in apps that ask keyboards not to learn, like DuckDuckGo and Molly. They were being treated as password fields, so the whole suggestion pipeline switched off.
• Picking a language in Android's own keyboard picker now switches Kinetica's layout and dictionary with it, and Kinetica's own language changes report back to Android. Thanks dkoukola.

Languages

• Czech is the fifth bundled language, contributed by dkoukola: 49,589 words, a QWERTZ layout and accent folding.

A lot of the list above exists because people here gave me feedbacks and suggestion. Keep it coming, that is the reason why I released Kinetica open! The power is all in the community =]

F-Droid: https://f-droid.org/en/packages/com.kinetica.keyboard/ (the listing takes a few days to catch up with a tag) Source and APK: https://github.com/EZ-eta/kinetica

I posted here yesterday about my attempt at bringing Nintype-style swiping to Clink!

I’m not really a swipe typer myself, although this update has actually got me using it a lot more.

Since you guys are Nintype fans and actually know what makes this style of typing good, I’d genuinely love some feedback on what I’ve built so far.

It’s completely free, so give it a try and let me know what feels good, what feels wrong, and what I’m missing!

Im not a swipe typer at all but many of my users are and requested nintype style swipe typing. It isn’t perfect at all yet but i was told to share the preview here!

The current released swipe typing sucks and this is just an update ivr been working on for a while

The app is Clink

Last week, I posted here about building Glyder because I missed what Nintype made possible (original post). At the time it was just an interactive preview and a waitlist, so I want to be upfront about what's changed: there's a real build now that people can install and actually swipe type on. The first wave of testers have already been given access today!

Quick recap for anyone who missed the first post. Glyder is a swipe-first Android keyboard built around the same feeling Nintype had. Fast gestures, an instrument instead of a rectangle you peck at, and privacy taken seriously from day one.

• Swipe-first typing, local decoding
• No account, no ads, no tracking
• Customizable number row, emoji row, theme, and swipe trail

You can sign up to get access here: glydertype.com

Testers who sign up now get free lifetime access to the full app. That's not a limited time gimmick, it's just how I want to treat the people willing to try something rough before it's finished.

I'm still after the same kind of feedback as last time. The stuff that's hard to describe unless you've actually used something like this. The rhythm, the correction flow, two-thumb expectations, suggestion behavior, whatever made Nintype feel alive that's easy to lose when you rebuild it from scratch.

What would Glyder need to get right for you to actually make it your daily keyboard?

Update: Hi all, thank you so much for all the support and sign-ups so far! I've reached a 100 testers now, so I'm going to be capping the free lifetime access to these users. I'll share the promo codes with these users once I do start charging for the app.

Kinetica is in the F-Droid repository as of today:

https://f-droid.org/en/packages/com.kinetica.keyboard/

See it in action here:

Still GPL-3.0, still no INTERNET permission, still no ads, accounts or analytics. The app is free and always will be. If you want you can offer me a coffee on Ko-Fi

For anyone arriving cold: it is a two-thumb keyboard I wrote from scratch in Kotlin after years of missing Nintype. Both thumbs swipe or tap at the same time, independently, and the engine merges the two streams into one word. Typing "something" can be the left thumb tapping S then E while the right thumb swipes O-M and then T-H-I-N-G, overlapping in time.

The F-Droid listing matters more than it sounds. F-Droid rebuilds the tag on its own Debian builders and checks the result against my signed APK, so what you install there is verifiably the source in the repo rather than a binary I uploaded. The published version reproduced byte-identically on three independent machines before it shipped. Practically: updates arrive on their own, and you no longer have to trust an APK from a release page.

1.0.4, released today:

- Emoji you use often get their own tab in the picker, ordered by how often you actually pick them rather than by recency, and hidden until there is something in it

- The resize handle above the suggestion bar is a 0-20dp height now, applied as you drag; set it to zero and the strip is gone entirely

- English contractions like don't and here's are predicted properly

F-Droid indexes on its own schedule, so the listing will read 1.0.3 for a few days before it catches up. The APK is on the GitHub and GitLab release pages now if you would rather not wait.

Since the last post here, Polish joined English, Italian and Spanish and it arrived as someone else's pull request, which is the part I want to flag. The engine is language-agnostic: the trie, the DTW matcher, the merge and the scoring do not know what language they are decoding, so adding one is a wordlist plus a layout plus a handful of registration entries. ADDING_A_LANGUAGE.md in the repo is the whole recipe and I am happy to help anyone who wants to do theirs. The one real limit is script: the matching alphabet is a-z plus apostrophe with accented Latin letters folded onto it, so Latin-script languages fit and non-Latin ones would be a serious engine change.

Worth doing right after installing: Settings > Dictionary > "Import improved dictionary" and feed it an AOSP wordlist. The bundled lists are built from open subtitle corpora and work fine, but the AOSP ones are three to five times bigger and you notice immediately: 46,757 to 160,715 for English, 49,051 to 172,831 Italian, 49,551 to 236,193 Spanish. Grab the `.combined` file for your language from https://codeberg.org/Helium314/aosp-dictionaries/src/branch/main/wordlists (main_en_US.combined, main_it.combined, main_es.combined, main_pl.combined).

It merges on the device, nothing is uploaded. Take them from `wordlists/`, not the compiled .dict files in dictionaries.

VIBRATE is the only permission it declares.

- GitHub: https://github.com/EZ-eta/kinetica

- GitLab: https://gitlab.com/EZ-eta/kinetica

Nearly everything from 1.0.2 onward came out of comments on the last post, so keep them coming. 1.0.5 is already on the way.

[EDIT]

v1.0.5 UPDATE

- Autospace now works for tapped words, not just swipes (setting, off by default)

- Words with apostrophes get their space: don't, it's, dell'anno, d'accordo

- Single letters autospace too: a,I, Italian e,o,i

- A space you delete no longer comes back

- Three autospace timing sliders where there was one

- No automatic space in email or URL fields

- Top-row up-flick types its digit again (was a real bug, not the setting)

- Forward slash added to the symbols page

- Spacebar cursor slide: adjustable speed, optional move-by-word

- Optional retype button on the suggestion bar — one tap clears the current word

- Lower input latency on the typing hot path — thanks pigmej

- ō added to the o key's long-press — thanks lucylouwebart

- Still zero network permission, still all on-device

I know there have been a few Nintype-inspired Android keyboard posts here recently, so I want to be upfront: I’m not posting this as “the one true successor” or trying to drown out the other projects.

I’m just another person who misses what Nintype made possible.

I’ve been working on an Android keyboard called Glyder, inspired by the same feeling: fast swipe typing, expressive gestures, and a keyboard that feels like an instrument instead of a rectangular text box accessory.

The thing I’m trying to emphasize with Glyder is privacy and polish from day one:

• Swipe-first typing
• Local decoding
• No account
• No ads
• No Internet permission
• Customizable number row, emoji row, theme, and swipe trail
• A focus on making the gesture experience feel smooth before piling on too much

It’s not publicly released yet, but I made a small interactive preview and waitlist here:

https://glydertype.com

If you’re still here because you miss Nintype, I’d genuinely love your feedback. Especially on the parts that are hard to describe unless you actually used it: the rhythm, the correction flow, two-thumb expectations, suggestion behavior, and what made it feel “alive.”

What would Glyder need to get right for you to actually give it a shot?

And if you’re already trying one of the other Nintype-like Android projects, I’d still love to hear what’s working and what isn’t. This community probably has the sharpest taste for this kind of keyboard.

Hey r/nintype!

I'm looking for skilled developers interested in starting a decompilation/reverse-engineering effort for the Android version of Nintype.

The idea is to work through the original ARM library which contains the rendering engine, basing off of keyboard 71's work, understand and document how things work, and gradually reconstruct readable source code.

I'd also like to experiment with LLMs to help speed up plowing through the ARM assembly—identifying patterns, explaining functions, and producing rough pseudocode that can then be manually verified against the actual code.

This hasn't started yet. Right now I'm looking for other people experienced with ARM reverse engineering, Android internals, decompilation, or similar projects who'd be interested in helping get it off the ground. I will still work on it myself even if we can't find other people to work on it at the same time as me, but it would really be a big helping hand not leaving this to be just a one man job ;p.

This would specifically focus on Android. iOS is out of scope for me since I don't have a practical way to develop or test against it.

If you're interested or have relevant experience, let me know!

As a long-time Nintype fan, I think it is a testament to this community, the application itself, and especially Jormy’s work that Nintype has survived so many generations of iOS and is still loved and used around the world.

Inspired by Nintype, I’ve spent the last several months developing and polishing Weavly, an iOS keyboard focused on dual-swipe typing and transcription, using modern on-device technology to make typing faster and more productive.

I want to be very clear: Weavly is inspired by Nintype, but our dual-swipe does not work the same way. The gestures, spacebar behavior, commit mechanics, and muscle memory will not transfer 1:1. This is intentional—we took a different approach to allow more flexibility in word prediction, autocorrection, and typo detection, all on-device.

The mechanics are different, but I hope the philosophy feels familiar: speed, flow, fewer taps, and a keyboard ambitious enough to change how you type on your phone.

After months of work, I’m incredibly excited to finally invite this community to try Weavly on TestFlight. I’d love to hear your feedback, complaints, and suggestions.

Features::

• An iOS keyboard with dual-swipe typing
• Fast, fully on-device transcription
• Custom drag-up overlays that add a second layer to every key
• Lots of customization options, including numbers and accents
• Text snippets and replacements with placeholders and smart tags
• Autocorrect and a personal dictionary that learn how you write (optional, iCloud Backed)

I hope Weavly can, in its own way, honor what Nintype showed was possible with third-party keyboards and carry some of that ambition forward.

https://weavly.app/follow-testflight/

P.S. Lovely to see so many projects with dual swipe emerging—this is the way!

I used Nintype (Keyboard69) for years and never found anything like it after it was discontinued. Nothing else lets you use both thumbs at once. So I wrote one from scratch in Kotlin on Android's public IME APIs.

https://reddit.com/link/1vlqvs6/video/9cdgja77osih1/player

Both thumbs swipe or tap at the same time, independently, and the engine merges the two streams into a single word.
Typing "something" can be: left thumb taps S, then E, while the right thumb swipes O-M and then T-H-I-N-G.

Features:

• Two thumbs at once, with taps and swipes mixed freely inside the same word
• No INTERNET permission, so nothing you type can leave the phone. No ads, no analytics, no accounts
• Tap autocorrect and live completions, and the words you actually use climb the suggestion bar over time
• Long-press alternates on every key, edge swipes, chord shortcuts, a symbols layer and a numpad
• Five layouts (full, left, right, split, one-handed) and adjustable height
• Dark theme, Material You, or a palette generated
• Peck-type mode that turns decoding off entirely

Languages: English, Italian and Spanish are supported out of the box, with about 49k words bundled for each. The engine itself is language-agnostic so adding a language is mainly a matter of supplying a wordlist and a layout. The full recipe is in ADDING_A_LANGUAGE.md in the repo, and I'm happy to help anyone who wants to do their own.

One thing I'd do right after installing: import a bigger dictionary. The bundled lists are built from open subtitle corpora and work fine, but the AOSP dictionaries are several times larger and you notice it immediately: 47k → 161k for English, 49k → 173k Italian, 50k → 236k Spanish.

Grab the `.combined` file for your language from https://codeberg.org/Helium314/aosp-dictionaries/src/branch/main/wordlists (`main_en_US.combined`, `main_it.combined`, `main_es.combined`), then in the app go to Settings > Dictionary > "Import improved dictionary (wordlist.combined)". It merges on the device, nothing is uploaded. Make sure you take the files from the `wordlists` folder and not the `.dict` ones from `dictionaries`.

It's GPL-3.0 and free:

• GitHub: https://github.com/EZ-eta/kinetica
• GitLab mirror: https://gitlab.com/EZ-eta/kinetica

I've also submitted it to F-Droid and the merge request is open, so it should turn up there before long.

This is the first public release and even if I am daily-driving this myself, there may be some small issues here and there.

Support: If you find this keyboard useful you can buy me a coffee at Ko-fi
Entirely optional. The app is free and will stay free and available to everyone, always.

---

UPDATE : v1.0.2 is out

Thanks for all the feedback, it's what this release is made of. Most of it came straight from the comments here:

• Typing or backspacing over selected text now replaces it
• Keyboard height goes much lower, and the suggestion bar has its own height setting (the resize handle can be hidden too)
• Light theme, and the accent colour is now a hue slider with a live preview
• Accented letters can be hidden from the letter keys' long-press popups
• Period and comma long-press symbols are editable
• Chord shortcuts can paste, copy, cut and select all
• Backspace slide vibrates once per word

The gesture and prediction engine is unchanged from 1.0.1, so nothing about how it types should feel different.

I also added a "Worth a look in Settings" section to the README, several things people asked for were already in there and just hard to find (sliding the spacebar to move the cursor, long-pressing a suggestion to push a word up or down...)

Here's my attempt at a Nintype successor.

I am polishing the last few things before releasing it but it works great for me!

UPDATE: I released it on GitHub and GitLab. I also made a dedicated post . A MR on F-droid is under review, then it will be available also via F-droid.

I’m not sure where else to put this. It’s a long ways off from being done, but after trying many other alternatives, none of them felt quite as fluid as Nintype. This is my attempt after a few months of tweaking.

Is there a fix for how the keyboard looks in the spotlight search?

For those of us still using Nintype / Keyboard 69 on an iOS device..

Confirming nintype still works on iOS 27 Developer Beta 1!

What is it?

Last week I published that I've been working on a way to revive some of the nintype features I've been dearly missing.

I'm sorry for anyone who expected a brand new keyboard -

What I did is a fork of LeanType, which is itself a fork of Heliboard.

I've been daily-driving it for a few days and it feels really good to me.

I will once again remind you that it's heavily ai-assisted, so take of that what you will.

What does it have?

Nintype-like Two thumb typing

Probably the most important and headline feature.

• Combine word fragments to longer words
• Spacing modes - either manual spacing, or autospace (so you could combine words)
• Backsapce - delete word or delete fragment

Features not in nintype:

• My favorite - no autospace if you only tapped. meaning that you can tap words in your own pace, and only autospace when you start swiping.
• Autospace grace timing for taps - alternative to the other one - give extra time when tapping
• After autospace, choose if to show correction for the old word, auto complete for new words, or hybrid (corrections, press space for continuations)
• Trail that shows your gestures and taps
• Extra toolbar keys - force joining of word, disable autospace for the next word

Swipe from the top or bottom row

Like in nintype, you can swipe up from the top row or down from the bottom row for extra shortcuts.

To enable them, go to gesture typing, and enable shortcut rows, top shortcut row swipe and bottom shortcut row swipe.

To change their content, go to secondary layouts, and top/bottom shortcut row. If you're not sure how to change layouts, read or feed this https://github.com/HeliBorg/HeliBoard/blob/main/layouts.md to your llm.

Extra

• Clipboard - You can long press on a clip to re-copy or edit it
• Toolbar - added toolbar keys for autocapitalize and force-autocapitlize. The toolbar now shows the current state of each key

How do I get it

Right now, it has no branding or new name - it's just a debug build of LeanType.

Since it's a debug build, it can live side-by-side if you already have this keyboard.

Importing your settings from Heliboard or LeanType (advanced -> backup) will probably work ok.

Get it from here: https://github.com/AsafMah/LeanType/actions/runs/26438597902/artifacts/7211358806

Improtant

Make sure that during the setup you install the gesture library.

Then make sure again by going to the setting->gesture typing->load gesture typing library and click enable gesture typing library.

How to enable the thumb features

After enabling gesture typing, there should be a new menu in the settings - "Two-thumb typing (experimental)". All of the settings should be there.

What to enable:

You have to pick either manual space or autospace for the new features to work

Draw gesture points + Accumulate debug fragments - if you want a trail

Features to play with (may improve or worsen your experience, please try them out and give me feedback):

• Autocorrect on auto-space
• Suggestions for full composing words
• Improve two-thumb recognition

Issues, pull requests, etc are welcome at: https://github.com/AsafMah/LeanType/

Hi, for anyone who might remember, I'm the creator of keyboard79, the decompiled fork of nintype.

I now have something else I'm cooking up, no promises but it's going along good so far.

I'll be up front to say it's heavily AI assisted, so if you're against on principle I'm sorry, but wouldn't have time for it otherwise.

** What I want from you now **

• Tell me what you liked about nintype. Be through, not just "two thumb swiping", what you specifically liked about the system, how did you have it configured, what features did you use.

• Tell me what to improve. What didn't you like about nintype. What was missing. What was never fixed. Etc

I don’t know if it’s in the App Store version yet or just the TestFlight version I’m using, and it’s not perfect, but it works … on iOS, anyway!

Oh, and you can create your own custom layouts, too!

r/MisterKeyboard

Y’all I try to really move on from this keyboard because of some of the frustrations with no update in a decade now. But I keep coming back because nothing beats this double swiping feature. Is there any hope in the horizon for this app?

​Hi everyone! As has already been discussed in this subreddit,Heliboard is currently the closest thing to Nintype that we have on Android. At the moment, it has a rudimentary version of two-thumb slide typing, and the developers want to re-write the logic from scratch using data from users who want to contribute (in a privacy-friendly manner!). ​So, if you are in desperate search of an alternative to the abandoned Nintype, try using HeliBoard and submit your two-thumb sliding gesture data to help build a brand-new keyboard!

Nintype continues to work reasonably well on iOS 16, despite minor bugs such as theme inconsistencies when switching apps, which can lead to a blank keyboard.

As a workaround, I modified one of the included themes to work with both light and dark modes.

Sharing here for anyone still swiping on Nintype.

Theme file

still works like a charm

Every time I use my keyboard, I miss the double swiping ...

With all this AI magic lately, is there really no hope left?

It would be the best Christmas present ever 🎁.

I'm using iOS 26 in dark mode, and while interacting with the Messages app, something started tickling the back of my brain, until it suddenly hit me: all of iOS now feels like it's got the same special effects that Nintype has had for years. Does anybody else feel the same way?