3 ms·

In my view, "polish" is rather orthogonal. For trivial apps that just assemble the building blocks that come out of the box, I'd agree. Otherwise, I find the "n

In my view, "polish" is rather orthogonal. For trivial apps that just assemble the building blocks that come out of the box, I'd agree. Otherwise, I find the "native" developer experience (XCode, Swift compiler) to be rather unpleasant. Moreover, the economics of developing "natively" limit the amount of polish you can actually justify.

ChrisMarshallNY 4y ago
The way to deal with that, is develop (or buy|integrate) dependencies that natively implement polish and chrome. For example, a UI framework may implement good transition animations. That’s pretty typical. Write an extension to UINavigationController, or UIViewController (if you use UIKit) that implements these transitions, package it as a standalone project, and integrate it, or simply have project-specific baseline framework extensions. That’s what I do. I have a ton of these packages[0]. It’s a fair bit of work, to do it yourself, but there are package[1] and extension[2] indexes. Caveat emptor. [0] https://riftvalleysoftware.com/work/open-source-projects/ https://riftvalleysoftware.com/work/open-source-projects/ [1] https://swiftpackageindex.com/ https://swiftpackageindex.com/ [2] https://swifterswift.com/ https://swifterswift.com/