This Week's Sponsor:

Textastic

The Powerful Code Editor for iPad and iPhone — Now Free to Try


Create New Byword Notes From Mr. Reader

Create New Byword Notes From Mr. Reader

I’m a big fan of Mr. Reader’s new services menu. Through URL schemes (documented here), it allows the app – a Google Reader client – to send selected text, URLs, or article titles to other apps. One of the custom actions posted by the developer allows you to create a new note in Byword, possibly formatted as a linked post for your blog.

The action (which you can download here) uses by Byword URL scheme to create a new note. In the note, you can have the article’s original title, some selected text, and a source link formatted as Markdown. As shown in the image above, you can modify the template with any characters you want. For instance, I added a > character before [TEXT-SELECTED] to format the selection as a quote block in Markdown.

I personally use Nebulous Notes and Poster to create articles for MacStories on the iPad, but a lot of folks like Byword. Check out the Mr. Reader action if you’ve been looking for a way to send text and links from Google Reader to Byword.

(Bonus: here’s a quick video showing the action)

Permalink

Chrome for iOS: Send A Webpage Back To Safari Via Bookmarklet

Sort of. Here’s a fun experiment.

Today, I wanted to quickly send a URL from Chrome for iOS – my default browser – back to Safari. I know there are ways to do Safari-to-Chrome, but I wanted the opposite: from Chrome back to Safari. I needed to install some custom Mr. Reader actions, and Chrome was giving an error when tapping on the downloadable files. I figured I could make a bookmarklet to take the current webpage in Chrome and send it to Safari.

Not so fast. There’s no documented URL scheme on iOS for opening web links in Safari, except, well, the http:// scheme itself. In testing various bookmarklet ideas, I thought that replacing googlechrome with http in Jon Abrams’ bookmarklet would force Chrome to send a link to Safari. But as It Turns Out™, doing this sort of trick in Chrome for iOS:

javascript:window.open('http'+location.href.substring(4));

…simply opens a new tab in Chrome.

What I ended up using is a hack – and a very curious one – to leverage Chrome’s support for x-callback-url to open a link back into Safari. I was inspired by Cormac Relf’s script, which I discovered yesterday when he showed me another script he made for Pythonista.

javascript:window.location='googlechrome-x-callback://x-callback-url/open/?url='+encodeURIComponent(location.href)+'&x-source=Safari&x-success='+encodeURIComponent(location.href);

As you can see above, we’re telling Chrome to open a new tab using…itself. The trick, at least theoretically, is to use an encoded location.href string to call back Safari, which is registered for the http:// scheme that Chrome, in this case, opens “externally”. Displaying x-source is needed per Google’s URL scheme specification; the name you give to x-source will be displayed as a “back” button in Chrome (as shown in the image above).

This is a profoundly inelegant and ultimately flawed solution. To make this “work” you have to:

  • Type the bookmarklet’s name, because Chrome has no bookmarks bar;
  • Nothing will happen.
  • Close Chrome;
  • Re-open it;
  • A wild new tab appears!
  • Tap the Safari button. It’s super-effective.
  • Safari will launch the link, closing the additional tab Chrome decided to open.

What is going on, exactly? Via JavaScript, we’ve forced Chrome to open a tab in itself, but doing so with x-callback-url inside a bookmarklet creates, for some reason, quite a strange behavior: the tab isn’t opened unless you close and re-open Chrome, therefore partially defeating the whole purpose of this bookmarklet, which is to quickly open a webpage in Safari. But, in spite of the clunky process, a new tab with a “Safari button” is created nevertheless, allowing you to tap it to launch Safari and close Chrome’s extra tab.

My conclusion is that we have three solutions: a) it’s not possible to create a straightforward Chrome-to-Safari bookmarklet; b) it’s possible in another way that I haven’t explored; or c) it’s possible with the x-callback-url hack, but in a different way.

If you have ideas, ping me on Twitter.



Sponsor: Newer Technology NuGuard KX

My thanks to Newer Technology for sponsoring MacStories this week with NuGuard KX.

The NuGuard KX is a protective case for the iPhone 4/4S and iPhone 5. The KX offers protection against accidental drops, impacts, and scratches without sacrificing looks or adding bulk. It’s been certified by Quanta Laboratories to withstand Shock Test Method of the MIL-STD-810G (U.S. Military Standard). And, unlike common military-impact test grade iPhone case materials, the NuGuard KX uses “X-Orbing gel” technology to absorb and evenly distribute kinetic energy. In one piece, the NuGuard KX offers access to all ports and buttons while offering an advanced protection.

Find out more about NuGuard KX here.


Temple Run 2: 20 Million Downloads In 4 Days

Temple Run 2: 20 Million Downloads In 4 Days

Imangi Studios has today announced that Temple Run 2, the highly anticipated sequel to Temple Run, has been downloaded over 20 million times in four days on the App Store. The original Temple Run was downloaded 170 million times across the App Store, Google Play, and Amazon Appstore.

Temple Run 2 generated 6 million downloads in the first day, making it one of the most successful iOS launches to date. Looking back at previous record-breaking numbers for iOS apps and games, Rovio reported 10 million downloads in 3 days, but on several platforms; the Google Maps app (also free like Temple Run 2) was downloaded over 10 million times in 48 hours. Imangi Studios also announced that Temple Run 2 is currently the #3 Top Grossing App on the App Store.

It’s no surprise that Temple Run 2 is doing well as far as in-app purchases are concerned. The game is clearly more optimized for IAPs, with unlockable upgrades, virtual items, and re-plays: if a player loses, he/she can choose to continue the same run using “gems”. Gems can be collected in the game, but they’re quite rare; the easiest way to get gems is to buy them. The “play again” menu is named “Save Me” and it appears in the middle of the screen every time a player reaches Game Over: it’s a very easy target to tap, it’s worded in a way to entice players towards continuing a run, and it mixes IAP with items that can also be collected in the game, albeit less frequently. For the developers, I believe it’s a very intelligent implementation of IAP (a subject we covered last year); for the players, it can become annoying because – as far as I can tell – there’s no quick way to dismiss the “Save Me” screen, which disappears after ~2 seconds.

Temple Run 2 is optimized for IAPs in other ways as well. Users can “like” Temple Run on Facebook or follow the game on Twitter to “get free stuff” (again, gems). In the in-app Store, they can buy coin packs, a “coin-doubler” upgrade, and gem packs that go from $0.99 for 5 gems to $19.99 for 500 gems. Unsurprisingly, the App Store page of the game reveals the top in-app purchases so far: the $0.99 5 Gem Pack, the $0.99 5,000 Coin Pack, and the $4.99 50 Gem Pack. I’d be curious to know the percentage of users who bought gem packs by following the “Save Me” button.

Speaking of Temple Run, make sure to check out The Telegraph’s interview with Imangi’s Keith Shepherd. In the interview, Shepherd talks about the history of Temple Run and their decision to rely on IAPs, but the first answer is my favorite. Making a game feel like a natural “extension of the player” has always been a top priority of another company that knows how to make games.

Permalink

Due’s Natural Language Input

Due’s Natural Language Input

I like Due. Both on the Mac and iOS, it’s a fast and easy-to-use reminder/alarm app with tons of options and iCloud/Dropbox sync. Due is simple yet powerful under the hood, as I’ve shown in my article on automating iOS.

I was playing around with Due again last night, and I noticed a nice detail worth its own mention here. Due supports natural language input for new reminders: you can write something like “Send email in 45 minutes” and Due will parse the “in 45 minutes” portion as a date input relative to your timezone. For instance, you can create a reminder on a Monday at 11 AM and write “in 2 weeks”, and Due will understand it’ll have to remind you after 14 days.

The way the developer got around parsing recognized language input is interesting. On iOS, if the app recognizes a date it will display it under “Set to…” in the title bar (a popover on iPad, as shown in the image above). Tapping that will set the date picker to your input. But there’s more: once set, you can tap again to remove the actual text from your reminder, because you don’t need the reminder’s name and date fields to say “in 2 days” at the same time.

Due for Mac comes with this subtle implementation as well. You can write something like “Meet Chris in 3 days”, hit Enter to accept the date, and the app will highlight the parsed text so you can hit backspace to delete it quickly.

It’s the little details that turn apps into great apps. Make sure to check out Due, and, if you’re geek enough, its powerful URL scheme.

Permalink

Predicting Apple’s Change

Predicting Apple’s Change

People have different opinions as to whether Apple should “change” or not. By “change” most people mean a “new hit product” or “changes to existing product lines”.

Here’s Michael Lopp, in November 2012:

Apple’s doom will start quietly and I doubt anyone can predict how it will actually begin. It will be historians who, decades from now, will easily pin its demise to a single event that will appear obvious given years of quantifiable insight. And it will only be “obvious” because the real details will have been twisted, clouded, or forgotten entirely, so it will all seem clearer, faster, and simpler. Their explanation will start with the passing of Steve Jobs, and they will draw a clear line to a subsequent event of significance and will say, “Here. This is it. This is when it began.”

John Gruber, last week:

Why just Apple? Why does no one argue that Samsung “needs” to unveil a major new disruption? What harm would Apple suffer if they spent the next five years refining and growing the products already in their stable? They’re already the most profitable technology company in the world, and their three major platforms — iPhone, iPad, and Mac — are all growing. They don’t need to change a damn thing.

John Siracusa, in our interview:

Apple needs to at least select its next big mountain to climb, even if it won’t be scaled for years to come. In 2012, Apple made louder rumbling noises about TV, but didn’t commit to anything. In 2013, Apple needs to put up or shut up about TV.

Apple also needs to start diversifying the iPhone line (as it did with the iPad mini this year), beyond just keeping old models around for sale.

Clark Goble, in response to John Gruber:

Here’s the thing. Not that long ago you could have said the same thing about Microsoft. However ten years ago I think the signs of their decline were already starting to be obvious. Fast forward to today and PC sales are stagnant, Win8 is a disappointment, their phone/tablet strategy failed, and Bing is still losing billions of dollars.

With Apple the signs are there too. Network services that still don’t work right and are unreliable. Design that seems to have lost that Apple strength of cutting out the unnecessary. They don’t “just work.” Important product lines that have gone ages without needed updates. (Numbers, Pages, Keynote, and arguably even iTunes since iTunes 11 was a disappointment to basically everyone) Even Apple’s famous ease of use and simplicity met its match with iOS’ system preferences.

I see both sides of the argument. For a company that was revolutionized by breakthroughs in innovation, it’s hard to imagine how they can avoid other major groundbreaking products for the next years. But on the other hand, with their three major platforms growing, why would Apple need to change anything now?

I think people have diverging opinions that are difficult to reconcile, both technically and philosophically. In the long term, perhaps Lopp is right – historians will look back at decades of Apple and understand what went wrong at some point in time. In the short term, perhaps Gruber is right – nothing needs to change.

I’d take a “the truth lies somewhere in the middle” approach. Apple is healthy, profitable, and still growing. But there are areas where they have shown they’re not infallible, such as services. They have problems that are far beyond leather textures and witty Siri jokes. I believe it’s fair to be concerned about Apple’s weakest areas, but I don’t think they spell doom for the near future. It would be silly to ignore those problems, just like it would be absurd to think Apple can go bankrupt next year. There are too many factors at play to ascribe today’s concerns as the single reason Apple “needs to change”. But it doesn’t mean we shouldn’t be criticizing Apple’s problems, or proposing better ways to solve them.

We can only wait.

Permalink

Dolphin Browser With Evernote Clipper

Dolphin Browser With Evernote Clipper

Dolphin, an alternative browser for iOS that I covered in 2011, has been updated today to version 6.0. Google Chrome is my go-to browser on iOS, but I had been testing this new version of Dolphin because of one feature: a native Evernote clipper.

Dolphin comes with lots of features and design choices, some of which I don’t like (case in point: the tap & hold popover menus). Given how Chrome keeps my tabs in sync across the iPhone, iPad, and Mac, I have no use for Dolphin’s Connect service and extensions. However, the built-in Evernote integration intrigued me as no major iOS browser to date has offered a native clipper for web content: some of them offered a bookmarklet-based clipper, but the experience of clipping URLs and text selection left much to be desired. Dolphin’s clipper is baked into the app, and it’s accessible from an action button in the toolbar.

The Dolphin clipper automatically grabs a webpage’s title and current selection (if any). It uses your default notebook as destination, and it lets you add tags and comments to a clipped item. Like the desktop Evernote clipper, you can save a full page, or just an “article” if the app recognizes you’re trying to clip a blog post. One thing I’ve noticed is that, in spite of my attempt to clip rich text, web clips from selections were sent to Evernote in plain text; when I chose “save full article”, Dolphin saved the page as rich text into Evernote, and quite beautifully as well.

A feature I really like is the possibility to annotate webpages before sharing them. This works with other sharing services in Dolphin, not just Evernote. There’s only a red brush and an eraser to choose from, but it’s enough to draw attention to a portion of a page and save it as a 768x924 .jpeg file in Evernote.

If you’re an Evernote user and have been looking for a better iOS web clipper, check out the latest Dolphin Browser for iPhone and iPad.

Permalink

Mr. Reader And The Services Menu for iOS

A “services menu for iOS” is a chimera advanced users and developers have long been trying to hunt down. It all started with a mockup Chris Clark posted in 2010, showing how third-party iPhone apps could offer their “services” – just like OS X apps – to the user through a contextual menu. The concept became popular fairly quickly, but, eventually, Apple did nothing.

Fast forward to 2013, iOS users are still asking for better integration of third-party apps with each other. Developers have resorted to using URL schemes, a rather simple way to directly launch other apps and pass information to them – usually bits of text. App Cubby’s Launch Center Pro has become the de-facto solution to create a “Home screen of app shortcuts”, offering a series of tools (such as automatic encoding and different keyboards) to make the process of customizing URL schemes as user-friendly as possible. Launch Center Pro is, in fact, the utility behind many of my favorite iOS tricks.

Pythonista has also become a big part of my iOS automation workflow. Combining the power of Python with the possibility of launching URL schemes, I have created a series of scripts that help me get work done on iOS on a daily basis. Further leveraging Greg Pierce’s x-callback-url, I have ensured these scripts can take a set of data, send it to other apps, process it, then go back to the original app. You can read more about Pythonista in my original article, and I’ve been following updates from developers who implemented URL schemes as well with a dedicated tag on the site.

I concluded my Pythonista article saying:

I believe that, going forward, Pythonista and other similar apps will show a new kind of “scripting” and task automation built around the core strenghts of iOS. As we’ve seen, x-callback-url is a standard that leverages a part of iOS – URL schemes – to achieve simple, user-friendly and URL-based inter-app communication that can be used in a variety of ways. Looking ahead, there’s a chance rumored features such as XPC will bring more Mac-like functionalities to iOS, but developers will still find new ways to make iOS more powerful without giving up on positive aspects such as increased security and the simplicity of the app model.

Mr. Reader – a Google Reader client that I’ve covered on MacStories in the past, and my favorite RSS app – has today been updated to version 1.11, which introduces a generic solution for launching URL schemes that shows how iOS automation is a growing trend, albeit substantially different from what we’re used to see on OS X. Read more