diff options
author | William Carroll <wpcarro@gmail.com> | 2020-04-19T12·05+0100 |
---|---|---|
committer | William Carroll <wpcarro@gmail.com> | 2020-04-19T12·05+0100 |
commit | 2fe6d7a10c8656de9a2e08e187486625d23c3535 (patch) | |
tree | d6b5869b94ef13d7ab081495c572e410b270e0d6 /haskell-file/f-todo.org | |
parent | 74ebb8e86997bffe98d4b062028d1b25740725ff (diff) |
Responsively size UI
TL;DR: scale down UI for non-mobile devices. I pulled the screen resolution for my phone, the Google Pixel 4, off of the internet. I created a device profile in Chrome to develop this application specifically for my phone. To my surprise, when I opened the app on my phone, many of elements that looked good in Google Chrome, looked askew on my phone. I needed to troubleshoot. Here's how I did that: I used Tailwind to responsively color the bg for each breakpoint to see if my device was sm, md, lg, xl (according to Tailwind's breakpoint terminology). After reading Tailwind's documentation and comparing their breakpoints with my Pixel 4's width (i.e. 1080px), I figured that my device would be lg. It's not; it's md, which I confirmed by using ngrok to load localhost:8000 on my phone and see that the background-color was "md:bg-green-600". I'm still unsure why my device is not lg, but knowing that my device was md was enough to fix many of the styling issues. My current theory is that while my screen's resolution is 1080 wide, the pixel density affects the media query for the breakpoint.
Diffstat (limited to 'haskell-file/f-todo.org')
0 files changed, 0 insertions, 0 deletions