Earlier this week, Apple released the first public betas of iOS 9 and OS X El Capitan, and, knowing that would be the case, I cautioned MacStories readers against leaving negative reviews on the App Store for third-party apps that developers can't update with new features and fixes yet.
It's worth pointing out that, at this stage, third-party apps from the App Store can't be updated to take advantage of the new features in iOS 9 and OS X 10.11, which could limit the potential benefit of trying a public beta for some users. On iPad, for instance, only Apple's pre-installed apps can use the new multitasking features in iOS 9. For this reason, users interested in installing the public betas should also keep in mind that developers can't submit apps and updates with iOS 9 and El Capitan features to the App Store – therefore, it'd be best not to leave negative reviews for features missing in apps that can't be updated to take advantage of them yet.
Unfortunately, since yesterday I've already seen tweets from the developers of two excellent iOS apps – Screens and Day One – post screenshots of negative reviews they've received by users who are unsurprisingly running into problems when using their apps on the iOS 9 beta.
What's even more unfortunate is that this happens annually for every single iOS and OS X developer seed, but I fear the problem will be exacerbated this year by the availability of public betas anyone can try. Therefore, this bears repeating.
Apple has apparently, via some sort of collaboration with a university professor, published last week — during WWDC — a really solid-looking learn-to-code curriculum for Swift that is kind of on iTunes U but that is really on GitHub.
I worried that “Metal” had become Apple's version of “Blast Processing,” a catch phrase in the 90s for the Sega Genesis. In commercials, Sega would gloat that only the Genesis had “Blast processing.” The only problem was, Blast Processing didn't really do anything that mattered.
But it turns out, I was wrong.
Metal for OS X is huge — and it's going to be a much bigger deal on the Mac than it is on your iPhone or iPad. If you use a Mac to produce professional content, chances are, Metal is about to drastically speed up the professional apps you use like Adobe Illustrator and Autodesk Maya.
Nick Arnott has taken a look at TestFlight a year after its relaunch and I agree with his overall take. I write about apps for a living (I currently have 74 betas in my TestFlight), and the simplicity of Apple's system is unparalleled. I just need to give developers my email and that's it.
I also agree with Nick's comments on frustrations with using TestFlight. I hope that Apple will continue tweaking these aspects going forward.
I've experienced a few minor frustrations with as a user though. For example, I can't accept an invitation from my computer — I have to accept an invitation from the device I want to test on. Also, TestFlight emails don't contain any release notes. With other services like HockeyApp, developer release notes are included in the email, so you can decide from the email if you care about the update or not. Lack of these release notes from TestFlight means you'll have to tap through to the app and view on your testing device to see if you want the update or not.
The common difficulties around implementing inclusive concepts in apps are a lack of resources, knowledge and empathy. All of Apple’s products have features that enable inclusivity, and they make a huge difference to people’s lives. Anyone developing for their platforms has access to the APIs to make their app equally accessible.
So how can we fix this?
From a user point of view, I want the Inclusive Toolkit to help solve two problems: unusable elements and poor experiences. And from a developer/designer/QA point of view, I want it to speed up development and testing time, as well as build empathy. It’s great if you work in a company that already has specific resources and knowledge about accessibility—but for many developers, that isn’t the case. I want to provide ways of making it part of the development process instead of something tacked on at the end.
Make sure to check out Sally's ideas for the Inclusive Toolkit, such as 'Visual Voiceover' and ways to simulate impairments in the app testing process. Too many developers still ignore inclusive design and features in their apps, and anything that could help them simplify implementing these frameworks is, I believe, welcome and necessary.
Ahead of its annual WWDC developer conference in June, Apple has opened up beta access to a new mobile app analytics service aimed at iOS developers. Simply called “Apple’s App Analytics,” an announcement inviting developers to request early access to the service appeared today on the iTunes Connect developer portal. Those with an iTunes Connect account can also reach the sign-up page using the direct link analytics.itunes.apple.com.
App Analytics are available for devices running iOS 8 and above, and the usage data part is completely opt-in. Every time you set up a new iOS device (or upgrade to iOS 8), you're asked if you want to share information with app developers to improve their apps through analytics. Other App Store metrics (views, installs, etc.) are returned for all users.
Based on the tweets I saw in my timeline today, first impressions seem positive. Apple can now give developers a level of insight that's unprecedented for any other app analytic platform. Apple's App Analytics can plug directly into the App Store and tell developers how customers find their apps, where traffic is coming from, and how many views an app gets on the Store.
iTunes Connect Analytics are such an incredible resource to have now. Feel like we were blind and now we see.
In the past few weeks, I've heard about a few timezone apps primarily designed to show world clocks that were rejected for unknown reasons, with developers annoyed about the lack of official guidelines. Today's change is better than approving and then rejecting an app, I guess, but maybe Apple could have shared this piece of information sooner. I don't know if those timezone apps ended up being approved or not, and there could be other developers with a different experience from the ones I talked to.
From Apple's standpoint, however, I can see why it makes sense to avoid confusion with apps that replicate a watch face UI – at least initially. It's not too dissimilar from Apple's stance on third-party apps that replicated native functionalities with the original iPhone App Store.
How do you break into business and the enterprise? We like Slack’s bottom-up approach. Start by making the best solution for individuals, who in turn advocate adoption for their team, who in turn evangelize to other teams…and up the chain it goes. If startups can make this strategy work in the Enterprise, as Slack has, then they can focus on creating a great experience for the end-user instead of a bloated feature list to pass a corporate approval checklist.
Hours is an excellent time tracker. I'm curious to see if this strategy will work out for them, and if other developers are tweaking their plans to follow a similar route.