iBeetle

A new car by Volkswagen with a custom docking station specifically built for your iPhone which allows it to draw information from the car and perform various other functions with the iBeetle iPhone app.

The Verge:

The docking station is designed to allow the iPhone to snap into the cradle, which will then provide owners with the ability to make use of the specially designed app. The app itself enables Spotify integration, use of a G-Meter, oil temperature gauges, fuel economy diagnostics, and a variety of social features — most of which should probably not be used while you are driving.

Seems like a really cool idea. I'm personally not a fan of the Volkswagen Beetles, but I'm excited to see this technology spread and grow.

Turning Off Your Devices During Takeoff is Unnecessary

A first officer for a major regional airline:

Flight attendants everywhere will hate me for this, but ... having your electronic device on below 10,000 feet is not an immediate danger to the flight.

I've always hated this rule and can't understand how it has managed to stay in effect this long. I seem to be in the middle of something important every time it comes into effect and it wastes a ton of my time. Hopefully we can abolish this useless law soon. In the meantime it just creates unnecessary fear, and people have been hurt because of it.

Mailbox opened to all new users.

The popular iOS email client Mailbox has finally removed the reservation system to gain access to the app. Now any new users can download Mailbox and use it immediately, hopefully without fears of overloading the servers.

The Mailbox Blog:

Good news! Mailbox is now available without having to wait in line. After 10 weeks of around-the-clock hard work, our engineering team has scaled the Mailbox service to deliver over 100 million messages per day (and growing). We believe we can now confidently handle new users as they sign up, so we’ve pulled down the reservation system.

I've been using Mailbox for a few weeks now. My personal email is an iCloud address, but I made the email account for comments and feedback for The Axx on Gmail because I thought Mailbox's advantages could be really useful for emails of that sort.

My experiment was a huge success. I think that Mailbox is a fantastic app, and I highly recommend it. The simple swiping gestures make it super easy to dismiss messages and send them to various places. I particularly love the time delay feature, which allows me to dismiss an email from my inbox and then be renotified of it and have it return at a later date. Mailbox makes it super easy for me to set up a quick swipe and tap and have the email return the next day at the start of my work day. (My work day starts at 1:30, since I get out of school at 1 on most days, so I was able to set my day to start then, and all emails that I dismiss for the next day show up right when I'm free to read them.) The feature works great and I use it regularly.

Quickly swiping away messages to archive, delete, time delay, or list them somewhere does an amazing job of helping me keep my inbox clear of clutter so that I know everything left in it are emails that I need to respond to right away. Mailbox has changed the way I view email, or more specifically, my inbox. I used to leave all my messages lying in the inbox after I read them, and I never moved them or did anything with them again. My inbox was basically being used as an archive. Now, thanks to Mailbox, I see the inbox as a launch board. My emails don't go there to be read and left forever, but rather, any messages there are those that I know require direct attention. As each message enters I swipe it off to wherever it needs to go, or time delay it right away. If anything is left afterwords then it is something that I'm actually replying to at that moment. This new workflow is great for me. It makes it easy to keep track of what's coming in and what I've replied to so that I never forget to reply to anyone's feedback or questions regarding myself and The Axx.

You can get your hands on Mailbox on your iPhone in the App Store today, and now you can actually start enjoying the app right away.

Ecoute 1.2

Ecoute is a beautiful music player app by PixiApps. It's my favorite music app on iOS, and Ecoute 1.2 is a fantastic update.

The biggest feature is one that I have been craving on iOS since I first got my hands on it in iTunes 11: Play Next. Now you can tap and hold on any album, playlist, artist, podcast or song and select "Play Next" to have that song added into the queue directly after the currently playing song is completed. No longer do you have to choose to either interrupt the song that is playing or wait until it finishes and then remember to tap the song you want next.

For those of us who use Launch Center Pro or Drafts, another exciting addition in this update is Ecoute's new URL scheme. You can now play, shuffle, or search for a particular song, artist or album in Ecoute via apps like Launch Center Pro or Drafts. If you have a favorite artist that you listen to often, you can set up a quick action in Launch Center Pro so that with one tap you can be listening to songs by that artist, and can even shuffle them.

I worked up a quick action to demonstrate the feature, to use it yourself just replace "the national" with whatever artist, album, or song that you wish to play:

ecoute://play?terms={{the national}}&shuffle=albums&repeat=all

That URL will launch Ecoute, find all songs by The National, play them in order in their albums, then shuffle to another random album by The National after each album finishes. The "repeat" parameter at the end will cause Ecoute to keep shuffling even after it has played through all albums.

Ecoute also supports shuffling by song rather than album, launching the app into the search bar, and various other useful actions. You can get more info about them on PixiApps' webpage on Ecoute's URL scheme.

The final feature in the 1.2 release is that Ecoute will now use last.fm to automatically download and display any missing album artwork, a good edition since Ecoute's UI is largely based around album artwork.

Ecoute 1.2 makes my favorite music app for iOS a lot better and more convenient, and I highly suggest you try it out.

On Teens and iPhones.

The results of Piper Jaffray's latest teen survey:

"We believe that despite the push from competitive products, particularly from Samsung, it appears Apple has solidly remained the platform of choice for teens," wrote Piper Jaffray senior analyst Gene Munster.

Being in High School (although only for another month, thankfully), I feel I may be able to offer some uncommon insight on this subject.

  • 48% of teens already own an iPhone, compared with 40% last fall
  • 62% of teens plan on making an iPhone their next mobile device (flat vs. fall 2012)
  • 23% expect to buy an Android phone, up from from 22% last fall

(The only other two digit percentage comes from the "don't care" category. Windows and Blackberry Phones are both in the bottom 5%)

Despite some doubt about this study due to it being unearthed that Apple has been an investment banking client of Piper Jaffray, everything I see at my own school, a typical middle class public high school, confirms it.

Here at CDO High School in Tucson, Arizona, iPhones are everywhere. I wouldn't be surprised if iPhones were represented at an even higher percentage than the 48% shown in the study. iPhones are most definitely considered the "cool" option, and I see kids with them from every group of people in the school. Moreover, there is no sign of iPhone growth slowing any time soon, as the social pressures inherent in any high school ecosystem have taken Apple's side, and iPhones are being pushed on non-iPhone users by other kids all around the school. It hasn't gotten to the point where not having an iPhone is a black mark upon you, but it certainly seems to be an indicator of status. Kids with iPhones seem to find every excuse to have them in sight at all times. iPhones are constantly laying in the open on desks or being held in hands, even while not in use, yet I notice non-iPhone owners are much less prone to flaunting their devices in a similar manner.

Discussions I've overheard or participated in with others on the subject provide a variety of reasons teens want to get their hands on iPhone more than any others. A common assertion is that iPhones, and Apple products in general, are the gadgets of choice in many universities, and students don't want to be stuck using a different device. Another popular idea is the obvious one, that everyone else in the school has an iPhone and people don't want to be left out. Many of those I know who own older model phones running operating systems other than iOS complain constantly about how slow and old they are, and discuss how eager they are for their contracts to expire so they too can join the leagues of iPhone owners. There are, of course, those who speak out against iPhones, but they are a minority overall in the school.

Overall, Apple has simply done an amazing job at entrenching themselves in the minds and hearts of teenagers. Despite the results of any studies or articles saying otherwise, I can easily assert that the demand for iPhones from the teenage audience is in no way waning. In fact, more teens seem to want iPhones than ever before. Certainly there is still a presence of Android owners, which while clearly not as large as the number of students with iPhones, is still a competitive force, but the loyalty of this presence to its chosen operating system seems to be shrinking much faster than it's growing. Android isn't in any danger of extinction in this high school's population, but the dominance of the iPhone is blatantly obvious. Apple would have to have a massive blunder to change the direction the iPhone's popularity with teens is heading. In the mean time, Piper Jaffray's study stands true.

Facebook Home for Facebook as a Company

I posted my thoughts on Facebook Home a few days ago, but to clarify, I was only talking about the user experience, which I find terribly disruptive and distracting, and would hate to use. In terms of an initiative by the company itself, I agree with Matt Drance:

If buyers start asking “does it have Facebook Home?” — and I think many will — that will be bad news for both Google and Apple. However, the Google – Facebook war is sure to be more vicious than the Google – Apple war because Google and Facebook have the same customers: advertisers. Users are their currency, and Facebook is about to rob the bank.

Facebook Home might not be great for many users, especially those anything like myself, but I know there are plenty of Facebook nuts out there, and if Home manages to find a niche of people who love it, and expands from there through word of mouth and as more phones are able to support it, it could very well be a great move by Facebook, and a huge blow to Google.

Nice move.

Facebook Home

Facebook yesterday announced their "Home on Android," or a new blanket layer over the standard Google Android UI, called Facebook Home. The biggest features of Facebook Home are Cover Feed and Chat Heads. Cover Feed overhauls your lock screen to show you items from your Facebook Newsfeed. This means you don't even have to unlock your phone to see what's going on on Facebook. Incidentally, it also means that no one else needs to unlock your phone to see your Newsfeed, either. Chat Heads, the other big feature, are a group of circles with your friend's profile pictures in them which float in the corner of your screen no matter what app you're in. Chat Heads are basically windows into your chat and messaging world on Facebook. When you get a new message or someone starts chatting with you, their Chat Head cycles to the top and you can read and respond to their message right there, without leaving the app you're in.

I haven't actually used it myself of course, and I don't use Android so I probably won't for a while, but I'm not really concerned, because Facebook Home sounds like something I'm going to hate. A lot.

Facebook Home, in terms of UI, is stunningly beautiful. I'm actually very impressed with it. It looks a lot better than the normal Android system, and from what I hear, it works really smoothly as well. But the problem is that Facebook is not as beautiful for normal people as it is portrayed as being by Facebook itself.

Ellis Hamburger, writing for The Verge:

Facebook’s images are stunning, but how does your lock screen look when it’s actually a stream of oversaturated Instagram photos and out-of-focus baby pictures? Or worse? As of this writing, the first thing in my News Feed is an image of a friend who used AMC’s "Dead Yourself" app to mutilate her face — a grotesque sight. The next photo is a group of friends in bikinis on spring break. The third is a friend’s selfie. When you install Facebook Home (or buy an HTC First), your homescreen will be whatever your friends are posting, no matter how good, bad, or downright terrible. When you press the sleep button to unlock your device, these are the kinds of images that will come to life on-screen.
[...]
If Facebook wants Home to really take off, it needs to realize that we don’t live in a world as beautiful as its marketing campaigns. It could limit "Cover Feed" posts to those only from your closest friends, or it could selectively analyze photos for quality content tagged to popular locations. Until then, I foresee many jokes that start something like this: "Dude, why do you have a salad on your lock screen?"

If you follow me on App.net, or know me personally, you probably know that I am extremely obsessive about my home screen and lock screen, perhaps a bit overly so. I keep them both looking good with really nice photos or other simple items. I never have pictures of people on my lock screen. If I had to look at my lock screen every day and see all the obnoxiously terrible pictures that my Facebook friends have posted, I would probably get really annoyed.

John Gruber at Daring Fireball:

That’s exactly why I described Facebook Home as a “nicely-designed phone interface that I would personally never want to use”. I don’t want photos from other people on my lock screen or as my home screen wallpaper. But given that they’re putting it into the Play Store, Facebook obviously thinks many people do want this. We shall see.

As for Chat Heads, those would annoy me even more. But I'm probably not the type of user they're aiming for. I actually use my iPhone for productive things almost all the time. I write and test URL actions on it, beta test apps, read news, check email, and much more. I already find it distracting enough when I receive short notifications for texts and other media coming to me while I'm doing more important things, how would I ever be ale to work if all those messages were floating at the corner of my screen at all times? If the heads of my friends keep jumping on top of each other in a crazy game of leap frog, vying for my attention and pulling it away from what I'm actually wanting to do? Sure, I'm probably in a minority for people who do actual work on their cell phones, but Facebook Home says it will be coming to Android tablets soon as well! Do you expect to be able to read a book or concentrate on important work on your tablet while levitating heads are bouncing around in the corner? I know I would find that distracting.

Here's Yoni Heisler on Network World:

Here's the thing about apps, and on a larger scale, technology that people love - no matter how much someone is into something, they don't want it thrust in their face 24/7.

It's why Gmail chat has an invisible mode. It's why iOS 6 has a "Do not disturb" mode. It's why people put their phones on silent. It's why people sometimes turn off Facebook Chat for good.

Yes, people want to feel connected, but they want to feel connected on their own terms.

With Facebook Home, it's the Facebook newsfeed 24/7.

I for one am very happy that it's unlikely Facebook Home will ever come to iPhone or iPad. It would be an end to the high level of productivity that I very much enjoy having when using my iOS devices, it would be an end to my pretty lock screens, an end to the lack of ads on my devices, and even an end to the fairly high level of privacy that an iPhone and iPad provides. I won't go into that, but Om Malik wrote a lot about the privacy concerns brought about by Facebook Home over at Gigaom.

Fantastical 1.1.1

Last week the popular iOS calendar app Fantastical released version 1.1.1. The most interesting aspect of this update (in my opinion) was the implementation of x-callback-url. This means that we can now send text to Fantastical through Drafts or Launch Center Pro, create an event from it, and then send the same text, or even more than that, to another app. To my knowledge, that makes Fantastical the first and, currently, the only calendar app that supports x-callback-url. In other words, a lot of workflows which we perform on a very frequent basis, involving the creation of events and scheduling and the like, can now be automated. Thus, I have created The Fantastical Action Series.

Good Company.

I have posted my thoughts before on the quality of people who frequent the realm of App.net on a regular basis. However, in light of recent events providing more examples, I've decided to acknowledge it again with even stronger emphasis.

Simply put, App.net is overflowing with wonderful people. Really, amazingly, undeniably great people. The friendships being made, the kindness being paid forward, and the conversations being enjoyed reveal the fundamental flaws in the cultures of all other social networks. These flaws take the form of envy, hatred, and general bad feelings being constantly passed around on the timelines and news feeds of Facebook and Twitter. The fact that something called Facebook Depression, fed by your jealousy of the "friends" whom you follow, even exists serves to prove this point. Twitter as well is a popular place for people commonly known as "flamers" to go after you with hateful comments if they even slightly disagree with the thoughts you post. Oftentimes they will do this just for fun, or for the benefit of their friends. A quote from an old article in The Magazine exemplifies the popularity of such comments:

"You love to send withering @ messages to people like Rush Limbaugh—of course, those notes are not meant for their ostensible recipients, but for your friends, who will chuckle and retweet your savage wit."

I won't claim purposeless assaults like these are completely absent from App.net, but they are most certainly far less common. Moreover, when hateful attacks do occur, there are usually a number of other App.net users who instantly leap to the defense of the target of the attack, reprimanding the offender and reassuring the offended that their presence and posts are appreciated. Still, the kindness and loyalty of the people in App.net is not even best shown in situations like the this. Rather, it is best shown in their selflessness and incredible generosity:

A few days ago, the battery on my old MacBook died. I know that I am receiving a brand new MacBook for graduation in only two months, so I do not want to blow $130 on a new battery for two months of use. Without any real expectations, I posted about it on App.net, asking if anyone happened to have on old MacBook battery lying around. To my surprise (although I shouldn't have been surprised), I received an inundation of helpful comments not only about where to go to get a cheaper battery, but people actually offering me batteries they still had from old MacBooks that they no longer use. Unfortunately, none of these batteries fit the profile for my early 2008 MacBook Pro, but had they, those offering them would have gladly shipped me their batteries. These are people I have never met, being kind for no reason except that they are kind hearted people.

It gets better though. Crazily better. A few days ago, one of our friends on App.net was going through a hard time, and was in the hospital. (I don't believe it was life-threatening, but in the hospital nonetheless.) She sent out a post about how she wished she would get an iPad mini for her birthday in a couple months. Unprompted, another App.net user, Matt Shirey, launched an operation under the hashtag #operationupsidedownfrown. Matt's goal was to raise and send the money to the hospitalized ADNer to purchase an iPad mini for her birthday. Matt sent out the first post, and many of us retweeted it to our own followers. Within no more than day and a half, contributions small and large from many different App.net users in the community were brought together, and we raised $320 and sent it to our friend in need. She will now be the proud owner of a brand new iPad mini, all due to the ridiculous kindness and generosity of the people of App.net. They didn't know her in real life, many didn't even follow her, but when all they heard was that Matt needed help turning her frown upside down, and that a tiny contribution from them could aid in this goal, they sent money. Could you imagine this happening in any other social network? With people who you had never met or even heard of, and who had never heard of you either? The correct answer is hell no.

Perhaps this culture of camaraderie and compassion is brought about because people don't want to pay money to be mean, but there are free tiers now, and I haven't seen any sort of shift away from this culture. Maybe it's for some other definable reason that I and others haven't been able to think of. Whatever the reason, it is undeniable that App.net is overloaded with the kind and the caring. These people don't envy each other to the point of depression. These people (or at least the vast majority of them) don't attack each other needlessly. On App.net we stand together, united by the pleasure of friendship and good company.

Trust me, you need to be here.

@axx

In fact, here are six free invites for App.net. Come make some new friends! (First come, first served.)

Launch Center Pro 1.1

Launch Center Pro 1.1 was released Friday morning, and it was a very impressive update. To those uninterested in advanced URL schemes and automated workflows the likes of which I cover on The Action Page all you'll want to know is that there was an overhaul on the Action Composer page, making it a lot easier to sort through, and there are now actions that allow you to access the clipboard and your photos.

However, for those, like me, who are interested in advanced URL schemes and automated workflows, you'll probably be a lot more excited about this update. Launch Center Pro 1.1 adds support for x-callback-url, Text Expander snippets, calling its own system URLs through URL actions and automatically converting text to various formats (like URL encoding/decoding). These improvements go a long way to making LCP more powerful, and useful in iOS automation. Still, I have found myself to ultimately be a bit disappointed in the update, because the potential that all these new features have created is not fully recognized.

x-callback-url

First and foremost, the implementation of the x-callback-url into an app centered around calling URL schemes should be a huge, huge improvement. Unfortunately, for no reason I can manage to understand, this implementation has been severely limited, because it only works for the system clipboard actions. In other words, the only use of the x-callback-url in this update is to copy text to the clipboard and then send the text out to another app using the [clipboard] variable. This can be useful of course, especially when paired with the new Text Expander support, but useful is not the same thing as powerful.

What I had been hoping for when I heard LCP supported x-callback-url was for an implementation of it in a very similar way to Drafts' implementation. I wanted to be able to make my own custom URLs, as I have always done in LCP, but then be able to call the custom ones via URL actions from LCP itself as well as from other apps like Drafts, and then have callbacks for when the actions finished. (Thus being able to chain multiple custom actions together, as in Drafts, but also making use of LCPs excellent clipboard and photo functionalities.) Drafts does this quite well, but Launch Center Pro has dropped the ball in its implementation of x-callback-url, at least in this update. For simple URL actions, using the clipboard functionalities with x-callback-url is convenient and a nice addition, but advanced URL actions and chains are still not possible in any particularly useful ways with Launch Center Pro 1.1. We'll have to keep deeper integration with x-callback-url on our wish list.

Text Expander Snippets

Here's where Launch Center Pro 1.1 starts to redeem itself. You can now insert shortcuts that you have created in Text Expander into your custom URL actions, and they will be expanded into the corresponding snippets when you run the action. You can also type your shortcuts into the dialogue box that pops up for prompts, and have them expand automatically. For an app like Launch Center Pro, which revolves around optimizing the speed of the simple actions you perform on your iOS devices every day, the integration with Text Expander is a great way to let you complete your actions even faster than before.

Callable System Clipboard Actions

Despite my overall disappointment with the level of x-callback-url integration, it has been done very well where it has been implemented. That being, in the new system clipboard actions. These actions allow you to place text or the last photo taken on the clipboard, or to convert the clipboard contents to text. Each of those three actions also has the option for a callback, or to allow you to send the text or photo to another app with a URL scheme that can accept the contents of your clipboard. Further, since these actions also have URLs of their own, you can call them from outside of Launch Center, or chain them together inside of Launch Center.

Other Features

There are also a few other features which are nice, but not particularly noteworthy. First, the new ability to tweet the last photo you've taken, something that was previously impossible to do even with the tweet shortcut built into Notification Center (you could only tweet photos by going through the Photos app, not counting using third party apps to tweet photos). Support has also been added for in-app email and message composition, which means you can finally send a message to a recipient not previously specified without leaving the app. Unfortunately, callbacks are not supported for the email and message actions, so even though they happen entirely in the app and an x-success parameter could be easily seen, there is still no way to chain any actions to the back of sending an email or message to someone (use Drafts for that). As a side note, I still prefer my Text Other action over the new built in messaging action, because although they now allow for the exact same result, using the Text Other action will move your cursor directly into the recipient input field so you just tap go and then are typing in the recipient name. In the built in action, hitting go from the prompt box brings up the messaging menu with your cursor still in the message field, requiring an extra tap to move to the recipient field. Not a big deal, but, in my opinion, the whole point of these shortcuts is to minimize the amount of taps required to complete actions. The last change I'll mention is the new layout for the Action Composer, which is still slow to load, but now a lot more organized and easy to sort through. It now has sections for system actions, installed app actions, all supported apps (with App Store links), featured apps (also with App Store links), recently added actions, and a custom URL button at the bottom. A minor improvement, but welcome, as the old Action Composer was a real pain to sort through.

New Toys

If you're looking for some new actions to try out which utilize the new capabilities of LCP 1.1, you can check out the ones in Federico Viticci's review, or head over to The Action Page, where I've posted some of my own.

@axx

The Due Later Action Series.

Idea adapted and modified from an article on I Miss My Mac by Jeff Kishner, who first adapted it from this article by Nathan Henrie.

Import any of the actions from the Due Later Action Series into Drafts to take a draft you write and create a time-delayed reminder to perform an action upon it later. When the reminder goes off, simply swipe the notification to open Due, and check the box next to the reminder to follow the URL action accociated with it. For dates or times until the reminder is to go off, use natural language input. Be careful though, because Due can sometimes mess this up if you write too complex of an input. Make sure to look at the beginning of your reminder to make sure Due didn't add that text to it.

iOS Automation

The History.

Automation of everyday tasks with scripts and interapp communications has been a tool for power users on computers for years. However, iOS has always been sorely lacking in the area. Apps on iOS are sandboxed, meaning they are only allowed to interact with the operating system in certain ways specified by Apple. It also means that they are severely limited in their ability to intereact with each other. This means that all apps are trapped in their own little boxes, unable to access anything except the basics, like pictures, contacts, and calendars. However, clever developers have managed to find a way around a great deal of these limitations: URL schemes.

URL Schemes

Much like how website URLs lead to specific pages within a website, app URLs can lead to specific places within an app. For instance, the basic "apple.com" URL will lead you to the home page of Apple's website, but if you type in "apple.com/iphone", you will bypass the home page and go directly to the page for the iPhone instead. App URLs work in the same manner. Using my favorite app, Drafts, as an example, if you type drafts:// into Safari on iPhone or iPad it will take you to the "home page" of Drafts. In other words, it will open Drafts as if you had just tapped on the app on your home screen. However, the power of URL schemes lies in the deeper integration. Just like adding "/iphone" in our example takes you deeper into Apple's website, adding terms to the end of "drafts://" will take you deeper into the Drafts app, and can even perform actions that would normally take multiple taps and swipes without you having to do anything except open a URL.

The Trick

App developers have discovered that URLs are one of the only things that apps are allowed to pass back and forth to each other while still staying in the confines of Apple's sandbox. They have exploited this trick as a sort of back alley root to allow interapp communication on iOS. Here's how it works:
If you're in Safari, Chrome, or any other web browser, and you type "drafts://" into the address bar and follow the URL, then instead of going to a web page iOS will leave the browser app and open Drafts app (assuming you have Drafts installed, otherwise it will do nothing). If you go deeper, you can type in something like "drafts://create?text=Hello World!". Then you will leave the browser and enter Drafts where a new Draft will automatically be created and populated with the text "Hello World!" Sounds cool, but kind of useless, right? That's where apps like Drafts and Launch Center Pro come in.

The Hub

Just like how iTunes used to be your "digital hub," where you would connect all your devices and sync all your apps and music, apps like Drafts and Launch Center Pro seek to become something like your "Communication Hub." These apps work by leveraging URL schemes to allow you to send text and actions out to other apps on your device. You type text into your "hub," and it distributes the text to anywhere you want, as long as the app it is sending to has implemented a URL scheme. For example, I can create an action in Launch Center Pro that will prompt me for text and then send that text to Safari which will perform a Google search of it. I can use this method to search in other places too: App Store searches, iTunes searches, Wikipedia, Terminology, Wolfram Alpha, Yelp, and many more, all from my central hub of Launch Center Pro. This means I can focus immediately on what I am searching for instead of wasting time finding the app to search from, finding the search box in the app, and then recalling what it was I was looking for. This same approach can be taken for many other actions besides just searching (i.e., texting, tweeting, posting to App.net or Facebook, calling a contact, etc.), and all of them can be performed from the exact same place. An avid user of Launch Center Pro myself, I can personally attest to the huge increase in speed and productivity that these methods can create. Still, while rapidly performing single actions from one spot is cool, it's not very complicated automation. That's where Drafts comes in. Drafts has taken Launch Center Pro's efforts even further, leveraging the power of the x-callback-url alongside a complex and robust built in URL scheme to allow users to chain multiple actions through multiple apps with a single tap.

The x-callback-url

The x-callback-url is a specification created by Greg Pierce. Pierce, not by conincidence, is also the developer of Drafts. X-callback-url is something that developers can freely implement into the built in URL schemes of their apps to allow them to send a "success" parameter after completing a certain action. It is very similar to an "if, then" statement in programming. If the app successfully performs a specified action, then do something else afterwords. This specification is what allows apps to chain back to one another. For instance, I can use Drafts to send text to Due, a reminder app. Due will prompt me to create a reminder with the text I wrote in Drafts, and when I successfully create the reminder, Due can then automatically send me back to Drafts. This would not be possible if Due's URL scheme did not include the x-callback-url: Due would then be unable to see when I successfully created the reminder, and thus would not know when to run the scond part of the action and send me back to Drafts.

The Automation

So with the combined powers of the Drafts URL scheme, the ability of apps like Drafts and Launch Center Pro to create and run custom URL actions created by the user, and the x-callback-url, automation is finally possible on iOS. Here's an example: one way for me to post to my website is by emailing an HTML document to a specific email address. When the message is recieved, it is posted to the site. I can do this on my iPad, but it takes an inordinate amount of time and many steps. I write the post as a draft in Markdown format, but then what? First, I copy the text, then I exit Drafts and open Notesy (A dropbox enabled note taking app that supports converting Markdown to HTML), then I paste the text into a new note in Notesy and convert it to HTML (which automattically copies it to the clipboard), then I close Notesy, find and open Mail, tap the compose button, paste the HTML into the body, type in a subject (used as the title of the post), and type in the recipient email address that will post the text to my site. All of this can take almost a minute, and it is an extremely clunky and annoying process. However, with the techniques for iOS automation that I mentioned above, I have managed to condense the entire workflow into a series of actions that can be triggered by one single action in Drafts, like a Domino effect. The action, renderMarkdown, first takes the text I have written in a draft in Markdown format and sends it to Notesy using the Notesy URL scheme. Notesy receives the Markdown and automatically converts it to HTML, then copies it to the clipboard. Drafts cannot (yet) create a new draft with text from the clipboard, but another great app for aiding in iOS automation, Pythonista, does have access to the clipboard. So the text is sent from Notesy to Pythonista, where a super simple Python script I wrote creates a Drafts URL action with the HTML from the clipboard as the text, and follows the URL. Drafts is reopened and creates a new draft prepopulated with my HTML, then calls an email action I made to create a new email message with the recipient address filled in with the necessary email address to post my HTML, and fills in the body of the message with the HTML itself. The only thing I do is type in the subject of the message and hit send.

All of that may sound extremely complicated, but in action the entire process takes less than five seconds between me running the renderMarkdown action and typing in the subject of the email. Everything else is done automatically, saving me quite a bit of precious time and preventing me from having to deal with the annoyance of copying and pasting and moving between apps and remembering the email address to send to, etc. This is the power granted to us by URL schemes, Drafts, and x-callback-url. This is the power that power users have been waiting for.

If you're interested in getting your hands on any of the actions I've made, or have some of your own you'd like to share with everyone, I encourage you to visit The Action Page, a page I've started right here on The Axx as a source for all advanced iOS automation actions and scripts, and to collect the latest news in this rapidly advancing new field for iOS.

Thanks for reading!
~@axx

Freemium.

Today, App.net introduced a free tier, effectively "going freemium." From the blog post making the announcement:

Although App.net has had only paid account tiers thus far, we initially conceived of App.net as a freemium service. It took some time to get to this point, but we are now ready to make this vision a reality.

So what does this mean? Well, that depends on who you are. If you're someone who has always been interested in the service, but were reluctant to make the payment required to join, or simply could not afford it, then this announcement is huge for you. You can finally gain access to App.net without having to pay a dime, and you can keep this access forever. (Instead of the month long free trial program that was previously in effect.) There are, however, a few limitations:​

Free tier accounts can follow a maximum of 40 users

Free tier accounts have 500 MB of available file storage

Free tier accounts can upload a file with a maximum size of 10 MB

This means, of course, that you will have to savor your limited amount of follows, but 40 is a decent enough sized number, and you can certainly live within this domain. In terms of storage, 500MB is definitely large enough to store all the photos you want to post to App.net for a long time.

These are actually very lenient limitations, and I could certainly see new users using the service perfectly fine within them. And if you're unsatisfied, $36 per year is really no that much at all.​

But what does this mean if you're a paid user? Well, for starters, it means ADN is going to become ​a whole lot bigger than you're used to it being. It means that you may get a lot more followers, and it means that you might find a lot more people that you will enjoy following. However, it also means that ADN as we know it could be in jeopardy. I posted just last week about what the App.net environment is like right now:

App.net is an ecosystem that has fostered an inundation of conversation and new relationships. I go to App.net every day not to get my daily dose of news, but an extra dose of camaraderie ​and confabulation to add to the real relationships I maintain throughout the day.

This is what ADN is to me. It's a place where I go to enjoy good company and have good conversations. It's not somewhere I go just to read rapid news flashes and hateful comments, and navigate through a sea of spam bots. That's what I was afraid of ADN becoming when I first saw the news come in that a free tier now exists.

But I should have known that Dalton Caldwell and the App.net team are not that foolish.​

To get access to the App.net free tier, you must have an invite. These invites are being distributed to current App.net members on paid plans.

So while App.net is now accessible for ​free, it is not​ accessible for everyone. By only giving out invites to members on the yearly paid plan, App.net has stopped a lot of the massive flow of users that would be coming in. Many of these users could just be spam bots and people who don't particularly care about the values App.net has been founded upon. Instead, the only way to get in is by a friend inviting you, or by actually going in search of an invite, which could be difficult, as they are going very, very fast.

This approach will very likely stop the vast majority of atrocities that we don't want to see or deal with on App.net, but still let in all the friends and interesting people that we have been missing on the service.

So, to conclude, I'm very excited about the future of App.net. Freemium is a method that has seen great success with services like Dropbox and Github, and I can't wait to see how it can launch the growth and success of App.net. I'm also very happy to see the App.net team is continuing to keep its users in mind, and not open itself up to the problems that completely free services like Twitter have no choice but to deal with.

​Let's see where this takes us.

App.net.

​I joined Twitter in October of 2011. For a long time, I failed to find any use for it in my life. After a while though, I settled in to using it as a news aggregation service, and a way to keep up with those I knew who also used it. I found that it was like a core feature of Facebook, except without all the extra fluff and bloating that Facebook packs around its status update service. I could see what my friends were up to without having to look at ads everywhere and having private messages, photos, likes, pokes, crappy games, and all the other excess that Facebook tries to shove down my throat. Twitter was quick to check, easy to understand (if you ignore hashtags, which have grown into so many purposes that they are quite hard for a beginner to understand), and just becoming "cool" enough that people my age actually used it. However, once I started getting more into technology, and began caring about the world outside of the little bubble of stress and drama inherent in every high school ecosystem, my use of Twitter evolved into something far more worthwhile. I began using Twitter as a news aggregation service. The 140 characters were perfect for super quick updates on the goings on of the world of technology and other areas of interest to me. I still kept up with my friends on the service, but I cared about it mostly for the links and quick updates about the field I planned (and still plan) on entering once I graduate.

My good will for Twitter, however, ran short quite quickly towards the end of last year, along with the good will of many others in the tech community. In a controversial decision that ​I won't discuss here, but that you can get summed up pretty quickly here, Twitter decided to put restrictions on its API to limit the amount of users that third party client apps could support, and to begin inserting sponsored advertisements into the timelines of those using the official Twitter clients. (There were, of course, more items of controversy, which you can read about at the aforementioned links, but those were the two main concerns.) In the midst of the ensuing uproar, a blog post from Dalton Caldwell received a great amount of attention. So much attention, in fact, that Caldwell decided to act on his ideas.

Enter App.net.​

App.net was at first hailed in the tech community as the savior from Twitter's new policies, but its attention soon tapered out. After rapidly ascending to over 20,000 users in the first few months, the rate slowed rapidly and at this point only around 30,000 users total have joined since the service launched in August 2012. The main reason for not only the initial popularity, but also the slow growth, is that App.net, unlike Twitter and most other social networks, is a paid service. To access App.net, every user must pay either $5 monthly, or $36 yearly. This, not surprisingly, discourages many people from joining the service. However, at the same time, it also terminates such annoyances as spam bots and fake accounts that litter Twitter's servers. Since the introduction of App.net back in August it has evolved from simply a Twitter alternative to a service that offers much more and has much room to mature, but in this post, I will only be focusing on the part of App.net that the unenlightened often call "a Twitter clone."

Twitter has a limit of 140 characters for every "Tweet." Before App.net, I had always just assumed this was the optimal number of characters for a microblogging service. After App.net, however, I now believe Twitter wasn't even close to this optimal number. App.net has a limit of 256 characters in each post. (There is, unfortunately, no catchy word for posts in App.net, like the word "Tweet." A few people attempted to title them "Dots" for a while, but it never stuck, and most of us have given up since then.) This may not seem like many more characters than 140, it's not even double, but that assumption is completely wrong. 256 characters has opened up App.net to a new realm  of communication. In order to stay within the bound of 140 characters, you have to relentlessly tear down your thoughts to their very essence, sometimes even less than it. With 256 characters, however, you are able to fit an almost unbelievably larger amount of worth into every post. Instead of cutting your thoughts down, you can post most of them in their true form, as they come to you. Having the ability to release complete thoughts instead of being trapped within the confines of 140 characters creates a fundamental difference between the two platforms, and has led to two distinctly disjoint ecosystems developing within them.

As I stated before, I go to Twitter in search of news. Rapid updates on what is going on and links to interesting articles I would never have otherwise been exposed to. In the past on Twitter, however, I posted very rarely myself. I didn't go to Twitter to make my own contributions, I went there to receive the contributions of others. Why? Because I didn't believe I was interesting enough to post my own thoughts and opinions. I didn't think anyone would care. This is an opinion shared by a huge amount of Twitter users. In fact, according to a study done by Diego Basch, around 50% of all Twitter accounts have never Tweeted once.

App.net, however, is completely different. ​I went to App.net with the intent of quitting Twitter. I wasn't looking for something new, I was looking for another place to find the news I enjoyed reading. As it turned out, App.net was not that place. I don't have any actual statistics for App.net, but I'm willing to bet a lot of money that far more than 50% of the users there have posted at least once, and most of them quite a bit more than that.

App.net is an ecosystem that has fostered an inundation of conversation and new relationships. I go to App.net every day not to get my daily dose of news, but an extra dose of camaraderie ​and confabulation to add to the real relationships I maintain throughout the day. I don't feel the same hesitation and anxiety I always felt about posting on Twitter. "Why should anyone care what I have to say?" "What's the point of posting if no one wants to read it?" These are feelings common on Twitter, yet practically non-existent on App.net. Go look at the first day of many of the people who have joined App.net recently. I'll bet that on almost every profile you see one, two, or even more people responding to the first post each person makes with a greeting. Something like "Welcome to App.net!" or "We're so excited that you're here!" These are the feelings that permeate the App.net environment. I feel completely comfortable entering into any ongoing conversation I see if I feel I have something to add to it, and those involved in the discussion will welcome my opinion with open minds, thanking me for my input if they agree or arguing back if they don't; but these are friendly arguments, not the type of flaming and yelling and spewing of hatred that opinions are often subject to on Twitter. This unique ecosystem leads me to go to App.net any time I have a question or comment on anything. Often instead of searching through forums or other places online for problems or inquiries I have, I now just go to App.net, and get a manner of friendly replies with helpful and knowledgeable suggestions. It's a much better experience, and one that I very much enjoy.

App.net has changed the way I view social networking. It is now, finally, truly social. We are a society of people who genuinely enjoy each other's company through an exchange of thoughts and opinions. Twitter is an unsocial network. Any place where new users are afraid to post because they don't think anyone will care or notice is not a place that can be considered social. Facebook is more social than Twitter, but not nearly as much as App.net. Facebook has too much fluff and excess that distracts you from the main purpose of joining together with your friends and people whom you respect and socializing with them. App.net, on the other hand, is purely social. There is nothing to do there except to be social. I don't know about you, but that's the type of network that I want to be a part of, and I am proud to say that I really am a part of it.

If you are reading this, whoever you are, wherever you come from, and whatever you do for a living, if you thirst for an environment to speak your thoughts and interact with other kind and interesting people, I encourage you to join us on App.net. We would love you to be a part of our conversations.

Twitter implements Ads API

In other Twitter related news, Twitter today released its API for advertisers.

From The Verge:

Twitter has released it API (application programming interface) for advertisers today, initially allowing marketers to work with a select group of partners to control, purchase, and manage their advertisements on the social network using third-party tools. The ads API enables marketers to integrate their Twitter advertisements with cross-platform management software, and they will also be able to customize Twitter’s tools to suit their needs.

In other words, if you use the official Twitter app or Twitter.com, prepare for more ads to be inserted into your timeline.

Of course, there are still ways to avoid this. Third party Twitter clients don't have to show the ads (Not yet, at least. Who knows what the future holds.), so I encourage you to try one of those if you don't want ads distracting you. I recommend Tweetbot, although I hear Twitterrific is excellent as well.

On a side note, the introduction of ads on Twitter is one of the reasons many people have left it for App.net. You get what you pay for, after all. (Again, I'll be posting more on this later today.)

On Tweetbot 2.7.2 and Twitter Display Guidlines

A few days ago, Mike Beasley wrote a blog post on how the updated Twitter display guidelines were going to affect Tweetbot. Oddly enough, Tweetbot just released version 2.7.2 to "meet Twitter's new UI requirements," yet they changed hardly anything. In fact, only one of the Guidelines Beasley wrote about caused a change that fully met the requirement.

No more name display options

Currently Tweetbot lets you show the name of a Tweet’s author one of two ways: their full name (Mike Beasley) or their username (@MikeBeas). The iPad and Mac versions also include a third option that shows both in the form of “Mike Beasley @MikeBeas.” Only third option is allowed by Twitter in the new Display Guidelines. The other two will need to be removed.

First opening Tweetbot, this guideline appears to be met. Tweetbot now defaults to the style of showing both the Full name and the @username. However, if you take a peak into Tweetbot's settings, the options to display only the @username or only the full name still exist. I reset mine back to full name only.

Right-side avatars are going away

As dictated by section 1c, avatars must appear on the left side of the Tweet content. Currently Tweetbot shows avatars for your own posts on the right, making it easier to quickly distinguish your own posts and follow conversations. Sadly, this is going away forever.

Unfortunately, this is the one guideline which required a change that Tweetbot was forced to meet. Now there is no way to easily discern your own tweets in your timeline from the tweets of those you follow, which I find quite annoying, and I don't really see what purpose Twitter saw for this guideline.

Left Side Avatars on your own tweets make it much more difficult to pick your tweets out of your timeline.

“Long form” dates are no longer allowed

There is currently an option in Tweetbot that allows you to show long-form timestamps on the timeline. This option will have to be removed.
This option was not removed, so if you are someone who chooses to use this style for displaying dates on your timeline, you can continue to do so. However, pairing the new default style of displaying both full names and @usernames with the style of displaying dates long form creates a nasty look where the dates cut off the @usernames with a "..." because both cannot fit into the small area (On iPhone). If this doesn't bother you then you can leave everything as is, but if it does (It bothers me a lot.) then you'll have to either disable long form dates or show only @usernames or full names. Luckily, all these options are still available.

The new default way of displaying usernames paired with the long form date style causes many usernames to be cut off with a "..."

Timestamps will now be links

Nope.

More in-app Twitter logos

I have still not been able to find a single twitter logo inside Tweetbot anywhere, much less always visible on the main timeline.

“View on Twitter” buttons

This section mandates the addition of a button on each user profile, Tweet detail view, or hashtag search results page that leads to the equivalent page on Twitter’s website or the the official Twitter app.

Unless I am missing them somehow, Tweetbot has no such links anywhere.

So all in all, our beloved Tweetbot remains relatively unchanged. The loss of our own avatars being displayed on the right side instead of the left like everyone else's is annoying, but not a huge deal. The fact that all the other options remain and most of the defaults have stayed the same as well makes me wonder what the purpose of these Twitter guidelines are if apps are not required to follow them. Or perhaps Tapbots is still just trying to see how much they can get away with before Twitter cracks down on them. 

I find all these Twitter guidelines senseless. If every guideline Beasley discussed, which Tweetbot did not already conform to, had been implemented, would they have done anything other than degrade our experience? Why should Twitter care whether we see the @usernames after every full name or not? Why should they care what side the avatars appear on or what actions are grouped together? Why does it matter if timestamps are clickable or not, as long as some other place in the Tweet is clickable for the same purpose? It seems like Twitter is just doing everything they can to make the lives of third party devs more difficult.

If you're as fed up with Twitter's foolish actions as I am, or are simply in the mood for some good conversations and pleasant company, consider joining us over at App.net. 

More on that later.

Update: I forgot to mention in the original post that these are only the changes made in the latest Tweetbot update, version 2.7.2. It is definitely possible, even probable, that in the future Tweetbot will have to implement more design changes to match Twitter's expectations. For now though, the above stands true.

Focus.

Focus is something that I often lack. I have little focus at school, and almost no focus at home. Realizing this last year, I set out to find a setting in which I could retain an attention span and actually manage to get work done. Quite surprisingly, I discovered that I actually do my best work in a coffee shop. At home, there are simply too many distractions. Chores pile up, the phone rings, family members come and go, and throughout it all the TV looms over the living room, quietly, yet irresistibly calling my name from atop its royal pedestal. Many people find the bustle of activity permeating through a busy coffee shop at any given time to be equally distracting, but for me it seems to have the opposite effect. At home, every distraction is magnified because they are all addressed specifically at me, but at a coffee shop, the distractions are almost never directed at me. People talk to each other around me, enter and exit, address the baristas with orders, and generally cause a commotion, yet none of this is in response to me, and none of this calls for any action on my part. Miraculously, sitting in a small bubble of calm amidst this storm of activity focuses me. I whip papers out in half the time it takes me when writing them from home while children yell and cry at the table next to me. I chain five apps together with URL schemes, Drafts, and x-callback-url while the people a few feet away argue loudly about gun control. I teach myself Python in a corner while the blenders and coffee grinders screech and the baristas call out names and drinks.

Of course, the downside of this procedure is that an inordinate amount of my somewhat limited funds flows into Starbucks' coffers on a weekly basis, but despite that fact, the rock solid focus this setting enables within me allows me to attack any challenge I choose with a will I wouldn't otherwise have been able to muster. This greatly increased level of productivity allows me to confidently conclude that every dime spent there is completely worth it.

If you find yourself suffering from a similar dearth of focus or attention span, I encourage you to go in search of your own place of zen. Perhaps you don't have the same calm-within-the-storm attitude that I am able to invoke, but I'm sure there are other environments in which you could experiment and find your own fit. Trust me, finding it will be well worth the effort.

Welcome.

Welcome to The Axx. Starting this blog is something that I have been planning for quite some time. Over the past few years I have become increasingly interested in technology (mostly that of Apple), programming, and designing. I began following people from the tech world on Twitter, as well as reading blogs such as Daring Fireball, The Loop, and Very Nice Website. Reading news, and opinions on it, from all these sources and blogs inspired in me a desire to have my own voice heard and to add my own opinions to the mix. I've always enjoyed writing, and starting a tech blog seemed like a great place to be able to write freely about a subject in which I am deeply interested.

Most likely, The Axx will never turn out to be solely, or mostly, a link blog, like the three I listed above. I will likely post some links to big news or other interesting things I see going on, and add my opinions on them, but I also plan to supplement that with longer posts and descriptions of projects I am working on or other ideas that come to my mind.

Recently, for instance, I have become very interested in URL schemes and inter-app communication between iOS apps. This trend began when I first read Federico Viticci's post on Macstories about iOS automation with Pythonista. I have since been working on my own techniques and URLs to achieve higher degrees of productivity throughout my day to day usage of my iPad and iPhone. This is one subject I will likely be writing a lot about here on my blog, and I look forward to sharing all the things I have done and learned with anyone who begins to follow my site.

I am really looking forward to my new journey, and I hope my opinions and projects can interest others as much as they interest me, so people may follow my site and enjoy my insights in the way I have been enjoying the insights of other tech bloggers. Thanks for reading, and I hope you return in the future.

Alex Guyot

Post to ADN