- Kotlin 90.5%
- Java 9.2%
- Ruby 0.2%
- Shell 0.1%
|
Rovanion Luckey
aad1cda3dd
WIP: Implement mini bottom control section
This change allows the user to esqew the control column for a pair of control buttons in the bottom row of the keyboard. In order to activate this feature, the user sets the new Layout > Control section field to "Mini bottom controls". With the option activated the middle column will be removed from the keyboard and in its stead one backspace key and one enter key will be added to the bottom row of the two main layouts. The main architectural change is the fact that rows are now exhaustively zipped when merged. That is, both the rows of the two layers are now consumed all the way to the end superseeding the previous behaviour of stopping once the first row stops. This commit is a first draft and contains some unsound code. The mini key entry does for examlpe not work properly in the letters or numbers only layouts. The function addBottomMiniControl also assumes that the bottom row contains one, and only one, button with a colspan bigger than 1. This is also the first time I write Kotlin, probably resulting in my added code being non-ideomatic or outright insane in some places. |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | Replace remaining references to GitHub with Codeberg | |
| app | WIP: Implement mini bottom control section | |
| benchmark | Stop using the deprecated kotlinOptions API | |
| build-logic | Migrate from gemoji to emojibase | |
| fastlane | Update fastlane metadata | |
| gradle | Update dependencies | |
| test-apps | Stop using the deprecated kotlinOptions API | |
| vendor | Migrate from gemoji to emojibase | |
| .editorconfig | Fix a bunch of trivial warnings | |
| .gitignore | Convert logo to adaptive icon | |
| .gitmodules | Migrate from gemoji to emojibase | |
| build.gradle.kts | Add autofillr test app | |
| CODE_OF_CONDUCT.md | Standardize on trailing commas | |
| CONTRIBUTING.md | Simplify and generalize a bit | |
| COPYING | License | |
| Gemfile | Update screenshots | |
| Gemfile.lock | Update screenshots | |
| gradle.properties | Enable Gradle config cache | |
| gradlew | Updated gradle wrapper to match lockfile | |
| gradlew.bat | Updated gradle wrapper to match lockfile | |
| PRIVACY.md | Optionally save emoji history | |
| README.md | README: Add missing setup step | |
| screenshot-app-keyboard.png | Keyboard-only screenshot | |
| settings.gradle.kts | Add autofillr test app | |
Logo FlickBoard - The Predictable Keyboard
(Logo by @MisterE123)
FlickBoard is a keyboard for Android that doesn't try to correct or predict you. It doesn't have an opinion on the correct spelling or tone. It certainly doesn't use any AI. Because it trusts you to write what you meant to write.
Instead, FlickBoard uses swipes to get away with using vastly fewer (and larger!) buttons than a traditional QWERTY keyboard, helping you build muscle memory, minimize typos, and touch type faster.
Type the letters in the center of a key by tapping it. Type the keys in the corners by swiping in that direction. It's that simple!
FlickBoard is inspired by MessagEase and Thumb-Key.
How do I install it?
| Get it on IzzyOnDroid | Get it on F-Droid | Get it on Google Play |
|---|
The latest release builds are also available from Codeberg Releases, but I recommend downloading from one of the above instead to get automatic updates.
If downloading from a source other than Google Play, you can verify using apksigner verify that
the
certificate matches the following SHA-256 digest:
51612a908aaf90aff66d1260a01992b3dde73a3ee3a94069412be2012272020f.
This should also match the digest listed at natkr.com.
You can also build it yourself, by cloning the source code
git clone https://codeberg.org/natkr/flickboard.git
cd flickboard
git submodule update --init
installing Android SDK and running the following on a computer that is connected to your phone:
$ ./gradlew :app:installPlainDebug
This requires the phone to have USB debugging enabled.
What does it look like?
| Screenshot of the keyboard in use | Screenshot of settings panel |
|---|
Why not MessagEase?
It's proprietary, and suddenly started requiring a subscription.
Why not Thumb-Key?
Back in the day, Thumb-Key didn't support MessagEase's more advanced gestures like circles and U-bends.
They do now, so this section is mostly historical, but FlickBoard's detection might still feel different, in ways that people may or may not prefer.