-
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
Android Question Layout...
- Thread starter kepler
- Start date
- Similar Threads Similar Threads
there are sevel ways, Kepler.
some use the tabview to jump to pages.
others use a sliding panels lib.
while other use a screen with buttons that either
- open new activity screen
- hide all panels and show the selected panel
the above can be done in the layout designer with just 1 layout as you requested.
For a small app I prefer the above but other people might like it to do it on another way.
But you have enough options
some use the tabview to jump to pages.
others use a sliding panels lib.
while other use a screen with buttons that either
- open new activity screen
- hide all panels and show the selected panel
the above can be done in the layout designer with just 1 layout as you requested.
For a small app I prefer the above but other people might like it to do it on another way.
But you have enough options
Upvote
0
It's like you build cars. Every standard car has 4 wheels but above these wheels every car is build for specific needs. A truck has a quite different layout than a roadster for 2 people.
Coming back to Android:
It's a simple fact that different devices have different screensizes. Some are full hd others have a very low resolution. The designer leads you to some sort of a compromise to handle it the same way.
First you should think of the basic design and what kind of app you want to create. Am I developing for a phone or a tablet? (f.e. do I build a car or a truck). A tablet has much more "space" (because it has a bigger surface). Users expect more data to see on their screens than on a phone.
As sorex said, you have a lot of options. There won't be ONE solution for all.
Coming back to Android:
It's a simple fact that different devices have different screensizes. Some are full hd others have a very low resolution. The designer leads you to some sort of a compromise to handle it the same way.
First you should think of the basic design and what kind of app you want to create. Am I developing for a phone or a tablet? (f.e. do I build a car or a truck). A tablet has much more "space" (because it has a bigger surface). Users expect more data to see on their screens than on a phone.
As sorex said, you have a lot of options. There won't be ONE solution for all.
Upvote
0
Similar Threads
