Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iPad Support #4662

Closed
chadyj opened this issue Jun 7, 2018 · 2 comments · Fixed by #4720
Closed

iPad Support #4662

chadyj opened this issue Jun 7, 2018 · 2 comments · Fixed by #4720
Assignees

Comments

@chadyj
Copy link
Contributor

chadyj commented Jun 7, 2018

User Story

As a user, I want to use Status on a tablet so that I can use Status on all of my mobile devices.

Description

Type: Feature

Summary: Status can be used on a iPad, but instead of running at native resolution the viewport is set to an iPhone 4 and everything is scaled up. Whilst the app is usable, it is a horrible user experience and doesn't take advantage of the devices resolution and screen real estate.

img_0041 png 2018-06-05 15-11-48

Expected behavior

Status runs at native resolution

Actual behavior

Status runs at a lower resolution and is scaled up

Solution

  • Make Status a universal app as outlined in this post.
  • Additionally, select all device orientation modes so it works in landscape mode too
  • Thoroughly test all screens at different tablet resolutions to ensure layouts look/work as expected
  • Fix any display bugs that arise
  • Bonus: Get split screen mode working (similar issue)

screen shot 2018-06-08 at 1 37 33 pm

@lukaszfryc
Copy link
Contributor

More screenshots of current iPad look: #4658

@chadyj
Copy link
Contributor Author

chadyj commented Jun 8, 2018

I did some testing with the fix mentioned above and many of the screens look great on an iPad. Here are several screenshots.

screen shot 2018-06-08 at 1 25 34 pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants