Optimize GitNex for large screens and tablets. #826

New Issue

Open

opened 2021-02-11 12:40:23 +00:00 by opyale · 1 comment

opyale commented

2021-02-11 12:40:23 +00:00

Collaborator

As screens keep getting bigger[1] and as mobile computing slowly gains more popularity[2][3][4][5], better support and use of large screens becomes important.

To achieve this, we should use activities only when neccesary and move our entire UI logic to fragments. This allows us to adapt to different screen sizes and improves overall reusability of already existing code.

Here you will find some documentation describing the steps necessary to achieve this goal:

https://stuff.mit.edu/afs/sipb/project/android/docs/training/multiscreen/screensizes.html
https://developer.android.com/docs/quality-guidelines/tablet-app-quality

Related to #600

As screens keep getting bigger[[1]](https://www.reddit.com/r/dataisbeautiful/comments/gv7t2f/average_mobile_phone_screen_size_over_the_years_oc/) and as mobile computing slowly gains more popularity[[2]](https://subredditstats.com/r/SamsungDex)[[3]](https://blissos.org/)[[4]](https://support.microsoft.com/en-us/topic/use-apps-from-your-android-device-on-your-pc-07d3d029-236e-e71f-3561-d40d7491d435)[[5]](https://mobilesyrup.com/2021/02/01/chromebook-sales-doubled-worldwide-2020/), better support and use of large screens becomes important. To achieve this, we should use activities only when neccesary and move our entire UI logic to fragments. This allows us to adapt to different screen sizes and improves overall reusability of already existing code. Here you will find some documentation describing the steps necessary to achieve this goal: https://stuff.mit.edu/afs/sipb/project/android/docs/training/multiscreen/screensizes.html https://developer.android.com/docs/quality-guidelines/tablet-app-quality Related to #600