I hope Apple chooses to give this problem the focus it needs. But that model doesn't work well for what many people think of as "productivity" apps. When the sandbox + App starts looking like a container instance running a unikernel, you've really supplanted the OS entirely. They have evolved into sort of microservice delivery applications. They started off as discovery, distribution, and payment processors. The response though will be even more interesting, either Apple can give application delivery the focus it needs and become the best in class example, or they can continue to languish, or worse they mandate by fiat use of feature which negatively impacts the brand.Īpp Stores try to be too many things at once. The key is that Apple has not pulled off a successful App Store concept for MacOS yet, and worse they haven't really internalized some of the things that make App Stores "good" or "bad". When it is done well, it enhances those things. In this case I think the parent comment combined with the GP comment capture the issue, when the App Store concept is implemented poorly, it negatively effects user experience, vendor experience, and customer satisfaction. I love when the top two comments on a story really nail it. Hidden behind a dozen trendy frameworks, a hundred bloated abstractions, and a thousand crusty layout engine implementation details to glue it all together. Meanwhile, iTunes and the AppStore continue the long and well-established tradition of poor integration. I'll grant you that this works OK on windows, but that's due to MS making the decision to bring the widget kit down to web-level rather than the other way around. > With a little effort they can be made to blend in perfectly. I'm curious, if you call drawRect ugly then what do you call the menagerie of frameworks required to strong-arm the declarative environment of the web into the simplest of desktop tasks (shadow DOM, anyone?) Pot, kettle? Imperative graphics and view hierarchies certainly make simple things tedious, but they'll never match the DOM's ability to occasionally make simple things nigh-impossible either. The very existence of PaintCode is an indictment. > What is 5 seconds of CSS takes a good 30 minutes of wrangling with NSButton/NSButtonCell. ![]() It'll take them time - they have enough cash to get there but they sure are alienating a lot of users and devs with these issues. Apple is getting better but as their data loss issues with Photos and Apple Music, as well as their problems with MobileMe show they are clearly finding it hard getting web devs who can build what they need fast enough. It took FB time to build the talent base to do a decent app (believe they even had to hire Loren Brichter to consult to help them with it!).Įvery company has its specialities. Their first mobile version was HTML with a native wrapper. Heck look at how long it took FB to come out with a decent iOS app. Chances are their current devs prioritise those kinds of apps over the kinds you might see Google or FB prioritise. Apple clearly have a lot of talent who know Cocoa and Obj-C inside and out. Without top tier web devs they of course will struggle to build scalable, fast and user friendly web apps. It's almost a chicken and egg situation where unless Apple builds top tier web apps they won't attract top tier web devs. Google and Facebook would likely be their top pick and not surprising since both of those companies are far more web centric - Apple has historically not been so. ![]() I don't think that most web developers looking for a job think 'Apple'. ![]() There is no excuse for reviews taking so damn long. getting them to update a 1-star review is nearly impossible. This should automatically give you at least a private way to send a message to users leaving a bad review, then prompt the user to update their review if the response helped them. I can only imagine this is due to Apple's inability to do good server-side software (and the organization doesn't value it like they value client software). This has been obvious since at least iOS v4. * Both iOS and the Mac app stores desperately need feedback mechanisms and some basic customer support tools. * Relatedly, add more entitlements to the Sandbox, even if they also trigger a more in-depth review. Put those apps through a much more strenuous review process. Have a "Power User / Developer Tools" category and associated checkbox in iTC that says "My app needs to opt-out of these parts of sandboxing". * Sandboxing is great, but there will always be things that fall outside the sandbox. Just make it a real native app and rewrite it. * The actual MAS store app itself is a horrible piece of garbage wrapping a bunch of web views. The worst part about this is all the problems are easily solved if Apple simply put the resources into it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |