florisboard / florisboard/florisboard
More optimisation for tablet style.
- Dominant language
- Kotlin
- Stars
- 8.6k
- Forks
- 732
- PR merge metrics
- No merged PRs in 30d
Description
I eould like to point out that I feel like your keyboard is meant for a portrait keyboard. When I use it on my tab, it feels like an strech of a small device keyboard to a bigger device.
There are button changes and a lot of changes in a tablet oriented keyboard like this.

And this is what Florisboard looks like out of the box (with minimal optimisation)

To not be biased, both are under same configuration. Its just one feels more natural and the other feels streched out. Sorry if this is insulting.
Contributor guide
Research direction
Start by comparing the two linked screenshots and reviewing the tablet-oriented behavior described in the issue. The issue names no files, tests, or entry points and does not define specific changes or completion criteria, so the scope would need maintainer clarification before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- design, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100