This week, the boys dive into iOS 9.3 with the help of Fraser Speirs.
On this week’s Connected, we discussed our first impressions of the iOS 9.3 beta and its implications for students and educators with Fraser Speirs. You can listen here.
Sponsored by:
Clever addition to Outlook for iOS just rolled out by Microsoft:
Innovation is happening in the calendar this week with our latest Skype integration. Make any meeting a Skype call simply by flicking a switch, then access the call when you need to with just a tap. Now when you say “I’m joining the call now”, you’ll actually mean it. To give it a try, simply turn on the “Skype Meeting” switch when creating or editing an event.
The integration generates a link to a Skype call that can be launched from the calendar event in Outlook. This works best for shared calendar events, so every participant can easily join the call and start talking.
I’m a big fan of Outlook for iOS, and this is exactly what Microsoft should be doing – leveraging their services to go beyond the traditional features of email and calendar. I like what they’ve been doing with Outlook.
Nice (and free) update to 1Password for Mac released today:
It’s a new year and we’re starting things off on a strong note with a great new update to 1Password for Mac: Version 6.0! This latest version of everyone’s favorite password manager is looking better than ever, and we couldn’t have done it without you. Your awesome feature requests, suggestions, bug reports, and usage scenarios really helped us decide what to include in this release.
If you use multiple vaults, you may want to check out the new functionalities in 1Password 6.0 (release notes here). I don’t, but I may reconsider this to set up vaults for my family and MacStories.
Also of note: AgileBits built a framework to use CloudKit JS for the version of the app sold outside of the Mac App Store. Apps that aren’t available on the App Store can’t implement iCloud support natively, but AgileBits figured out a way to use CloudKit technologies for web apps in their Mac client:
From our customers’ point of view, iCloud Sync in the AgileBits Store version of 1Password will look a little bit different during the initial setup. CloudKit JS does not use the iCloud settings from OS X, so to authenticate with Apple, 1Password will prompt you to log in to your iCloud account by displaying the iCloud login page in your default web browser. Once you have logged in to your iCloud account, CloudKit web services sends an authentication token back to 1Password, which it then stores (securely, of course). This enables 1Password to sync with iCloud without having to reauthenticate each time. Since the iCloud login for CloudKit JS is completely separate from the iCloud settings in OS X System Preferences, you can even use a completely different iCloud account if you like!
I don’t know whether I should be impressed that AgileBits created this workaround or sad about Apple’s decision to restrict iCloud to the semi-abandoned Mac App Store (maybe a bit of both). AgileBits plans to make AgileCloudKit open source, too.
I received a 1st generation iPhone as birthday gift last year from a good friend of mine and I really haven’t done much with it. I started wondering if the phone could be used day to do if needed and if so, what the experience would be like today.
So, I thought it might be fun to have a look at what the most popular websites today look like on that incredibly revolutionary device.
If you think about it, the “winner” among websites that work well on an original iPhone today isn’t a surprise. I wish more websites adopted that strategy as well.
This morning, Twitter announced a new Periscope integration with the official Twitter app on iOS: starting today, users will be able to start watching Periscope live streams directly from the Twitter app without having to jump to Periscope.
From the Periscope blog:
Since launch, there have been over 100 million broadcasts created on Periscope. Whenever a broadcast is shared on Twitter, you tap the link to open the Periscope app. Today, we’re replacing those links with the broadcast itself, autoplaying right within the Tweet. And when you tap the video, it goes full-screen and shows Periscope comments and hearts from other viewers. You don’t need the Periscope app or even a Periscope account.
And here’s Casey Newton, writing about the new integration at The Verge:
In-line Periscopes are designed to look like a hybrid between the two platforms. “This brings the Periscope format to people who have never experienced Periscope, or don’t know what Periscope is,” says Aaron Wasserman, a Periscope engineer. Tap a video in the stream and it will expand and begin to play sound. You can view the comments and hearts inside a broadcast on Twitter, but if you want to comment or send hearts yourself you’ll have to tap a button to open it inside Periscope.
At the same time, you can interact with the broadcasts the same way you can with other tweets: liking them, retweeting them, or replying to them. That last one is important: Periscope broadcasts are limited to 100 commenters; Twitter replies mean that big broadcasters are likely to hear directly from more viewers.
According to Periscope, they’re also considering an option to store some streams permanently for preservation purposes. The Twitter timeline keeps gaining media previews and integrations that aren’t available in other clients – I think native Periscope playback for streams makes a lot of sense.
In addition to iOS 9.3, Apple released the first beta of tvOS 9.2 today. Benjamin Mayo has a rundown of what’s new at 9to5Mac:
With the new Apple TV tvOS 9.2 beta, Apple has added a whole host of new features to the tvOS platform. This includes support for pairing Bluetooth keyboards, Folders organisation for apps on the home screen, a new App Switcher UI and a native Apple Podcasts app.
There are also some enhancements to Siri and other improvements. Apple has added support for two new Siri languages: US Spanish and French Canadian.
There was a ton of work left to do in the first tvOS – and I’d argue that the software shouldn’t have shipped without Remote app support – but it looks like Apple is catching up quickly.
The Wall Street Journal reports that Apple has mistakenly been underestimating the number of readers using Apple News and providing those inaccurate numbers to publishers:
Eddy Cue, Apple’s senior vice president of Internet Software and Services, said the company missed the error as it focused on other aspects of the product. The company didn’t explain how the problem occurred or say exactly when it might be rectified.
“We’re in the process of fixing that now, but our numbers are lower than reality,” he said. “We don’t know what the right number is,” but he added that it was better to undercount than overcount traffic.
A curious admission from Apple, particularly given that the issue has not been fixed yet. No details are given about the scale of the miscalculation, so it’s unclear as to whether this will result in a minor adjustment or significant adjustment in reader statistics.
Executives from Apple, including Mr. Cue, met with publishers late last year to discuss the product and address concerns. Mr. Cue said Apple will continue to spend a lot of time getting feedback from publishers.
Two months ago there were a few reports, including this one from Digiday, which noted that publishers were “underwhelmed” and “dissapointed” by Apple News, and the reader numbers.
I find the iOS Videos app frustrating to use. It’s almost unbelievable that in the 9th major version of the OS it’s missing what seem to be some pretty basic features. However, this also means that it should’t be hard to make it a lot better:
This is a great list of suggestions for the built-in Videos app by Michael Tsai.
The Videos app strikes me as one of the most outdated Apple apps across iOS – it was updated with a basic UI refresh for iOS 7, but its functionality largely remained unchanged. There’s a chasm between the video experiences on Apple platforms – with the new Apple TV now out of the door, I think a complete revamp of the iOS Videos app should be taken in consideration this year.
There’s a petition on SumOfUs.org, calling on Apple to keep the standard headphone jack on the iPhone, following more reports that Apple is planning on removing it with the next iPhone.
This is right out of the Apple corporate playbook. A few years ago it swapped out the original iPod-dock connector with a new one, making countless cords, cables and chargers obsolete.
Apple plays up its green credentials, but the truth is that Apple only invested in renewable energy, and began phasing out toxic chemicals when public pressure became too strong to ignore. People power did it before, and we can do it again.
Tell Apple to keep the standard headphone jack and ditch planned obsolescence!
Look, this is a ridiculous and hysterical petition which blows the situation completely out of proportion. But having said that, the fact that this petition (on a website I’ve never heard of before) has exceeded 200,000 signatures in just a single day just goes to show how big a task Apple has if it does decide to remove the headphone jack with this year’s iPhone (remember, these are just rumors for now).
Last month, when these rumors first started circulating, I took the time to document some of my own thoughts about how Apple could minimize the frustration of consumers – as well as explaining why it will be a more painful transition than the 30-pin to Lightning switch, and some other tangential questions that this scenario raises. I don’t want to rehash it all again here, but here’s a snippet:
In essence, I think Apple should do three things. Firstly, acknowledge the trade-off Apple have made and the frustration some customers may feel. Secondly, clearly enunciate the benefits of switching away from the 3.5mm audio jack to the Lightning connector and Bluetooth audio. And thirdly, make the customer’s transition away from the 3.5mm audio jack as painless as possible. I’ll leave the first two up to Apple’s marketing team, but I do have some thoughts on the third.
Who knows if these rumors will even turn out to be true, but there’s an awful lot of smoke already. But even if it doesn’t happen with this year’s iPhone, it will inevitably happen – and when it does, expect an almighty backlash. The real question is how many steps Apple takes to reduce the pain to consumers.
(Via 9to5Mac)
