florisboard / florisboard/florisboard

More optimisation for tablet style.

Open
#962 4 comments 0 reactions 0 assignees View on GitHub
proposal
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.

![Screenshot_20210529-222515](https://user-images.githubusercontent.com/74511929/120082648-beb00480-c0cc-11eb-9adc-dc62238964b8.jpg)
And this is what Florisboard looks like out of the box (with minimal optimisation)
![Screenshot_20210529-222606](https://user-images.githubusercontent.com/74511929/120082667-dedfc380-c0cc-11eb-9b96-9aa53b001990.jpg)
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

Open the contributing 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.