Also, the App Store is a client for remote data (what's on the store). What should one expect to see when there's no connectivity? A local cache of all app data? That could be feasible, but also not very useful (you still can't buy or download) and might be misleading (e.g. an update might have been added or taken down etc).
It's not that there's no connectivity. Whatever they're using for metadata is extremely slow. As though all requests need to go to California or something.
> A local cache of all app data?
Yes. This is how Linux package managers all work; metadata is cached locally so search (and dependency analysis - not needed in AppStore) performs well.
Maybe put some pages explaining when you would need this functionality, that you have to be living in this country, etc. Or you could also limit the amount of times a user does it for maximum once in a month or less. And so on.
There's a lot of good alternatives, having bad UX should never be one of them.
Otherwise your users are just going to solve it their way, like in my case, where I had to create another account and backup all my stuff from the old account simply because I moved from my country.
For example, the iOS Camera app hides away options for the frame rate and resolution of video under several menus. This option is much more accessible in actual cameras. In Apple's case, it's put out of easy reach to prevent the user from obsessing over which resolution to capture a moment, and to provide a uniform appearance to all captured content.
Options are hidden away to reinforce a set-it-and-forget mentality.
There are a number of buttons that do follow iOS style though. Also, "Redeem" and "View information" open up views that were previously unavailable except through iTunes, and you can see a mishmash of styles there too.
The two things that infuriate me though are the font size of the sidebar, and the laughably placed "Done" button on the top right when you're viewing a story.
You mean the actual sidebar (with the top level note folders) and the notes list? That has been the norm in 99% of note apps (and similar 'bucket' apps) for ages, across platforms...
Having said that, I suspect the use cases of notes are quite varied, so a one-size-fits-all approach might not be straightforward.
So?
They've been working on this for a while.
Well, they can save files (like Apple's own audio notes app), connect to the network, and so on. So what access do they lack? They're not on the same direct kernel? That's probably for the better.
They are on the same kernel. As far as I'm aware, they're in the same namespace as well, so this isn't just a simulator, either.
If you mean the current 4 iOS app running on 10.14, then i agree. If you mean project Marzipan in general and what it means to developers, well we just don't know yet. Its going to be the next WWDC at the earliest before we hear any new information on the topic and its overall goals/capabilities are yet to be fully defined.
https://github.com/w0lfschild/macOS_headers/blob/master/macO...
https://github.com/w0lfschild/macOS_headers/blob/master/macO...
This thing will be massively popular once mature. Whether that’s a good thing for MacOS in the long run, I don’t know.
When Marzipan was first announced, Apple was very careful to temper people's expectations. Marzipan is not about some grand new cross-platform development framework. It's not about merging Mac and iOS. It's about allowing iOS developers to port certain iOS apps to the Mac with as little friction as possible.
And in that sense it's a complete success. Many 3rd-party apps can already run inside of Marzipan with little or no code changes. That's a huge win.
There are some very obvious downsides. Most iOS apps are a poor fit on the desktop and won't conform to the expected Mac desktop expectations. I suppose Apple could have gone the Windows 8 route and put these iOS apps in a completely separate environment, but we all know how that turned out on Windows. At least these apps attempt to mesh with the regular desktop environment.
Another downside is that it's a hack. These are pure iOS apps running inside of an iOS simulator designed to look like a Mac app. These apps have no access to the world outside of iOS.
If you're looking to make a great modern Mac app, Marzipan isn't for you. If you're looking for an easier way to share UI code between your AppKit and UIKit apps, Marzipan has nothing for you. If you have a relatively simple iOS app that you think might be useful on a Mac, Marzipan is exactly what you've been waiting for.
If you want a peek into what a grand new cross-platform development framework might be, take a look at the JetEngine.framework embedded in the Mac App Store app. It appears to be a separate UI framework that is neither AppKit nor UIKit, but can run on top of either. However, it's full of App Store-specific UI components and I would expect that it was developed only for internal use at Apple.