3 ms·

For some reason, the justified text is unreadable on iPad.

• Joel_Mckay 2y ago
  If you have ever had to deal with iOS/mobile web, than the reality of trying to deploy Media Queries hits hard. Don't take this the wrong way, but making something pretty for 2% to 14% of users is often low priority. Dealing with AppleWebKit client side is often challenging for developers looking to integrate normal features found in Chrome/FF. The CSS gets ugly fast... but some folks like that kind of perpetual project. lol =3
  • lelandfe 2y ago
    "Looks bad on iPad" usually means "looks bad within 768-1024px." There are lot of other tablets out there that belong within that range. (iPad-specific problems do exist and are a bummer) > The CSS gets ugly fast Mobile-first keeps things happy if you're writing one big CSS file or even stuff like SCSS. Use as little specificity as is needed, and generally use min-width instead of max- so that your CSS is written "mobile first," in a cascading manner. Responsive and readable CSS is possible at scale, it just requires some dedication.
    • Joel_Mckay 2y ago
      The better frameworks I've seen used a template abstraction layer to render different interfaces for mobile, pad, and desktops. Every iPhone version was slightly different, and if the scaling is wrong the GUI glitches look like an amateur hatchet job. =3
  • miohtama 2y ago
    It is not very difficult to create websites that work on every device. Most websites work fine with every device and very little effort is put towards this.
    • Joel_Mckay 2y ago
      If one doesn't care about pixel perfect presentation, than workable results are possible with 3 templates. However, if you are doing something that requires each graphic/font to fit the layout properly, than it is often 38+ devices you will be supporting. =3