4 ms·
Android apps being required to target api 26 by August 2018. The urgent need for safe area support for the iPhone X. Reading about these annoyances of nat
by TekMol 8y ago
Android apps being required to target api 26 by August 2018.
The urgent need for safe area support for the iPhone X.
Reading about these annoyances of native development reassures me to keep building web apps. They are so much more future proof.
- rimliu 8y agoSupport for iPhone X is trivial unless you’d made bad choices before. Anecdote, but as having extensive experience in both areas (20 years web, 9 years iOS): natives has way way less annoyances.
- pjmlp 8y agoSure, because handling div soup and CSS across browsers is so much fun. https://www.youtube.com/watch?v=eVnUDTtOLE0 https://www.youtube.com/watch?v=eVnUDTtOLE0
- hesarenu 8y agoget familiar with modern web development!
- pjmlp 8y agoI am painful familiar with web development!
- jazoom 8y agoGP said "modern"
- pjmlp 8y agoI am painful familiar with "modern" web development! Happy for being pedantic?!
- jazoom 8y agoIt's not pedantry. That word was the whole point of his/her comment! And if you're painful (sic) familiar with modern web development why are you still creating div soup?
- pjmlp 8y agoI don't know, maybe because web components still aren't a thing across all deployment targets? That Web designers are still playing catchup with native RAD tooling from the 90's? That React devs so enthusiastically re-discovered how 90's UI were keeping up to speed with slow hardware? Or maybe because GPU acceleration requires CSS tricks with Z-Order to actually work?
- jazoom 8y agoNone of that has anything to do with my question, but okay. Never mind.
- DonHopkins 8y agoBut "modern" with ironic air quotes is totally different than earnestly unquoted modern.
- hesarenu 8y agoWe'll you seem to think they work on Chrome Safari. I develop on Firefox and test on others. From other comments you seem to be a desktop developer now reluctantly working on web. Targeting just windows OS would be simpler and easier I agree. But we have moved into multi platform now. Needed to up the skills. That said for native apps be it desktop or mobile using native tools would be the way to go.
- tzahola 8y agoI check out "modern" web development from time to time. What's the state of the art in 2018? Can you have a DIV with a fixed aspect ratio fitted to the screen? Last time I've checked (in 2017) this was impossible without JS.
- detaro 8y ago> Can you have a DIV with a fixed aspect ratio fitted to the screen? It's admittedly far from obvious, but that should be doable by determining the height of the DIV with the padding-top of a child element, and limiting the width with max-width limited to at max height * aspectratio, so it doesn't overflow the bottom if the page gets to wide. Not really anything fancy and new in there either. EDIT: s/width/height, added half sentence explanation.
- tzahola 8y ago>limiting the width with max-width limited to at max width * aspectratio Sorry, I don't understand this.
- detaro 8y agowhops, height not width. Code: max-width: calc(100vh * 16 / 9);
- tzahola 8y agoOk, this works only for fullscreen because of vh. Let's say I want this to work within another DIV too, so you can't use vh. (and the parent DIV's size is flexible, so you can't hardcode it into calc(...)).
- ricardobeat 8y agoFlexbox can handle that.
- 8y ago
- rhodysurf 8y agoBoth of these things are easy if you just don’t use react-native
- k__ 8y agoI don't understand. I added iPhone X support to an RN app rather ad-hoc a week before it was released. While I had a few issues with the resolution, safe-area wasn't one.
- ricardobeat 8y agohttps://facebook.github.io/react-native/docs/safeareaview.html https://facebook.github.io/react-native/docs/safeareaview.ht... Has been there for at least 6 months.