uberspot/2048-android

Better Scaling

Open

#60 opened on May 10, 2018

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Java (1,026 stars) (802 forks)batch import
good first issue

Description

Here is what 2048 looks like on my screen. I could live with this if at least the touch detection was fullscreen.

Contributor guide

Tech stack
javaandroid
Domain
mobile
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Android developmentUI scaling conceptsTouch event handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Investigate how the game board is currently scaled in the layout (likely in activity game.xml or the GameView class). Consider using a FrameLayout with proper scaling to fill the screen while maintaining aspect ratio. Ensure touch event coordinates are mapped correctly to the scaled view. Check if any existing comments or PRs discuss scaling approaches.