Let's think about how to make buttons bigger and more finger-friendly

[NomadicVoxel]

Problem Description

The problem is simple: we're adapting a GUI that was designed for a mouse.

Good job on making the UI more compact to fit, but there's still the issue of buttons being sized for a mouse. My fingerprint covers like three or four entries on the job board, for example.

Related Issue Links

Text scaling is kinda a relevant issue, and I think patching that might help this somewhat, but not all the way. https://github.com/thewierdnut/endless-mobile/issues/30

Desired Solution

Here's a few simpler ideas:

• Bigger margins on buttons
• Bigger line height on lists
• On the map screen, panels can overlap. Maybe move the panels around. Give the job board the entire height of the left side.
• For lists with collapsible sections (like the Outfitter shops), maybe collapse the sections by default. And perhaps put a green asterisk on ones with items the player can afford, and a blue one on items the player had never seen before.

Alternative Approaches

More complex ideas:

• Do what Chrome Mobile does when it receives an ambiguous tap: screenshot the area around your fingerprint, and magnify it, and have the player try again.
• No room for several big buttons? Replace several with one that hides and reveals them! Such as moving the Job Board's sorting buttons to a row under the title line, and where they were before, add a button to hide/reveal that row.
• Collapsible sidebars: Make large panels the entire height or width of the screen, but just shove them off screen until someone selects the relevant menu button.
• Screen panning: Move the entire frame of view so the element the user is focused on is centered vertically.(Particularly renaming a new ship, or typing the Captain's name to confirm you want to delete a game. My keyboard covers it.)

Additional Context

No response

[thewierdnut]

Every change I make to the mobile fork is a change I usually have to re-implement when I rebase on the upstream project. My preference is to push changes like these upstream if possible, and I am working on these issues already, but the upstream project has a slow pace of development for UI changes.

These changes are coming. Stay tuned.