I have a program called WWPointsPlus that have many users. Today one of the users says the botton row of buttens are cut off. The sreen size is 320x240. How do I prevent this problem, and test for it.
-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
Sceen size
- Thread starter bobsimoneau
- Start date
- Similar Threads Similar Threads
Upvote
0
What is another way. How many Layout Variants is reasonable? What do most of the programmer here provide?
400x800?
320x480?
320x240?
320x240 seems like to little real estate to work with.
Upvote
0
After hours of work I have decided to give up on coding for QVGA screens. 320 x 240 is just not enough real estate. I added a disclaimer to all my apps.
Upvote
0
If you are distributing via the Android Market, check your statistics. You can see the phone models that are using your app.
These stats are really useful and helping me to tailor my app to my users.
Neil
Upvote
0
Up until now I had all four of my applications on the market with only a 320x480 Layout Variant. My phone is a HTC Incredible at 480 X 800 WVGA resolution. I have a single emulator setup exactly like my phone (480x800). Recently I changed a program from using internal keyboard and added a key board onscreen. This app allows for portrait only. At least two users have complained the keys are cut off, They appear to have 320x240 screens (Motorola Charm) and display sideways. Looking at google statistics as suggested was only part useful, 59% list as other. My apps are all free and ad free. I just want to give everyone a chance. What layouts do most use here, and what emulator sizes do most test on. Since my phone is 480x800, should I be using that layout variant. Sorry for being long winded, but I am confused. I am just trying to figure out what is best practices.
Upvote
0