If you currently sell a paid-up-front app on iOS and Mac, there will be some customer expectation and pressure to make your app universal. I don’t have a lot to say to these folks, except you are correct. If Apple makes a “universal” buy once-run-on-any-Apple-device binary possible, the customer expectation is likely to shift, and people will simply expect to have to pay only once. Some developers make iOS and Mac versions of the same app and sell them separately for a one-time upfront price. This will negatively impact some businesses That’s no reason for the rest of us to keep using clunky tools. In the hands of lesser developers, any tool will be used to create crap. The problem here isn’t the tool, but rather the people using the tool.
#Ios emulator for mac december 2017 full#
There are some apps, however, built with universal storyboards that take full advantage of iPad. They don’t use the extra power and screen real-estate available on iPad in any fundamental way.
The result was a ton of new apps that now run natively on iPad but are little more than “blown up” iPhone apps. Looking at the disparity between the number of iPhone apps and iPad apps available, Apple decided getting more apps on iPad was a priority. When Apple made universal storyboards available on iOS, the promise was it would now be easier to make apps that run great on both iPad and iPhone. This will lead to a repeat of iPhone and iPad Universal apps Find your little niche and set your business model accordingly.
#Ios emulator for mac december 2017 software#
And there never will be.ĭevelopers who care about making great software keep wanting the majority of people to give a shit. There aren’t many people in either group. People who care to make good software will make the good stuff. Here’s the thing: People who care about good software will find the good stuff. A few thousand more bad apps will be a blip on the radar. They will try to make a quick buck.īut who cares? The last time I checked, there is already a ton of crap available on the Mac. It will still take time and effort to make a good Mac app, and many developers will not bother. Remember how many terrible watchOS apps debuted minutes after watchOS was made available? Apps that had no place on the Watch, that tried to do way too much on the Watch, that didn’t understand the utility of the Watch, and so on? That will absolutely happen on the Mac, too. Thousands of previously iOS-only apps will end up on the Mac barely altered with bad UI on day one. This will lead to a lot of crappy iOS ports on the Mac But to me, the good outweighs the bad here. Let me start with the short version: Yes. However they go about it, the million-dollar question is: Would this be a good thing? Rather than a straight port of iOS’s UIKit to the Mac, as some have requested from Apple for years, Marzipan would more likely be a new framework that replaces both AppKit and UIKit in favor of something more modern and clean.
And thus, perhaps you could even create (and sell) a single app binary that is capable of running on either platform, if you choose. Obvious differences between the platforms would necessitate some variation, of course (clicks vs taps, and all that), but the underlying APIs for creating either would be largely the same. Ĭode-named, Marzipan, this new framework would help developers who make either iOS apps or Mac apps to make both using the same basic toolset. At least, that’s the part of the rumor that makes the most sense, anyway. Rumor has it Apple is cooking up a new framework that helps unify the development of macOS and iOS apps.
0 kommentar(er)
