You’ve almost certainly seen these posts flying around Twitter and other social networks this week, but did you read them? Or did you just scan the title and think “Oh I knew
React Native wasn’t a good idea!” :grinning:
I’m not a huge fan of React Native myself, and obviously this isn’t good
news for the technology, but Airbnb’s decision is more subtle than you might first think. I’d suggest reading all five parts: 1
“iPhone Only” apps on the iPad
I agree with Ben Dodson that it’s ridiculous that iPhone apps must
run on the iPad in phone mode. There’s a minor, but significant improvement to the situation coming with iOS 12 though. :tada:
Join the Swift Community Spectacular :hatched_chick::tada::bowling: in New York City on September 3rd – 5th. Learn the latest in Create ML, Siri Shortcuts, Swift on the Server, SwiftNIO, Memojis (how to make your own!), and much more! In-depth workshop topics include Cryptocurrency, Function Composition, Kotlin, Accessibility and more to be announced! Use code TRYIOSDEV
by next Friday to get $100 off!
Repeat after me, “I will never hard code the height of a navigation bar, tab bar or the status bar in my iOS apps”. Then go and read Geoff Hackworth’s article on some changes you may not have noticed. :grinning:
This new text styling library from Ryan Nystrom looks good. It not only assists with a flexible, concise way of building attributed strings but also provides a bitmap renderer (and an associated
to allow those bitmaps to easily end up in a view hierarchy). If you’re struggling with performance when rendering lots
of attributed text in a table or collection view then you’ll want to check this out.
Was the reason that 3D Touch was never adopted by developers because users didn’t know it was there? Or did a luke warm reception from users prevent developers from putting in the time with it? This post by Eliz Kılıç suggests that it was because there was no obvious UI showing that 3D Touch was possible. I really like this idea.