Circling around on the internet over the last few days has been the news that there is a patent application for the “pull-to-refresh” feature that Loren Brichter pioneered in Tweetie and is now an extremely popular UI gesture used in a lot of iOS, Mac and Android apps. Twitter holds the patent application, not Brichter who recently left Twitter after they acquired him and Tweetie a few years ago. It’s also important to note that the patent has not yet been granted, it is simply a patent application at this point in time.

Featured in the latest One More Thing podcast (a tie-in to the Australian iOS conference we wrote about last week, featuring many of the speakers), Brichter briefly talks about the patent (note that this was actually recorded before the news about the patent spread wildly on the internet) and says:

… I can’t talk about the specifics but Twitter owns the patent, but I don’t think people have anything to worry about.

Brichter also describes the design process that resulted in the “pull-to-refresh” feature being implemented in the episode. He talks about how in Tweetie 1.0 the refresh button would be on top of all your tweets because there wasn’t enough room on the navbar because of a back button and compose tweets button. But for Tweetie 2, Brichter thought he could “make it a little simpler” so that you didn’t have to scroll to the top, lift your finger and tap on the refresh button, instead he asked the question:

…why not just make refreshing part of the scroll gesture itself? So it was kind of an obvious extension of a simple idea.

The whole episode is certainly worth a listen, Brichter offers some great insights on development and his experiences as both an independent developer and a developer working in a large team (like he did for Twitter and Apple).

Thanks to Stuart Hall for the heads up.

Tweetbot, Tapbots’ excellent Twitter client for iOS that we recently reviewed for the launch of its long-awaited iPad version and 2.0 update on the iPhone, received today support for one of the most requested functionalities by its users: streaming.

Available today in version 2.1 of the iPad app, live streaming allows users to stay on top of the latest tweets thanks to Twitter’s real-time push technology that can be seen in the new Tweetbot timeline, which, when on WiFi, will constantly check for new tweets and automatically load them above your timeline position. An option is available to disable streaming in the app’s Settings, as well as a switch to enable “Pin to Top”. In my tests, Tweetbot’s new streaming feature has been extremely reliable — that is, unless Twitter itself was experiencing issues — and has enabled me to forego completely the need of manually refreshing or waiting for Tweetbot to update my timeline every few minutes. Like on Twitter for Mac, I think streaming is an invaluable tool if you’re planning on getting the most out of Twitter’s real time nature, and Tweetbot’s implementation doesn’t disappoint.

With streaming come a few other changes to make the experience of fetching and syncing tweets more pleasant. The new tweets sound, for instance, is now limited to mentions, direct messages, and tweets fetched with pull-to-refresh. The Tweet Marker service, which allows you to keep your Tweetbots (and other supporting clients) in sync, has been vastly improved. Generally, this means the process of getting your latest-seen tweet and timeline position should sync faster to the cloud and back to the app — in testing the latest Tweetbot, I can confirm Tweet Marker sync seems a little faster and more “accurate” than before.

Tweetbot is my favorite Twitter client on any platform, and streaming makes it a lot better from a user experience standpoint. You can get iPad update from the App Store now (the app’s graphics are also ready for the new iPad coming out later this week); version 2.1 of the iPhone app, sporting the same new features and Camera+ 3.0 integration, is still waiting for approval in the App Store’s queue.

- Tweetbot for iPhone

- Tweetbot for iPad

Since its release in April 2010, the iPad has been widely regarded as a “consumption device” not really suited for “content creation”. Whilst we have already examined the issue with dismissing the iPad as a device that’s not capable of doing the same things a computer can — and my friend Shawn has a good take on why “content” generally is an awful marketing umbrella — the Storify iPad app, coming today for free on the App Store, is yet another example of how the iPad is changing the way we create through unique interfaces built around touch and the strengths of iOS.

Storify is an interesting service. Per se, Storify isn’t strictly focused on allowing you to create original content (images, text, or a combination of both) that you can share with your friends; rather, Storify is a curation tool that, among other services, leverages Twitter and the openness of the web to let you create “social stories” based off elements shared by people you follow, or just about anyone else on the Internet. Storify wants to tell stories by “curating social media”. I have covered the topic of curation — especially Twitter curation — several times on MacStories, and I recently mentioned Storify in my review of Tweet Library, an iOS app by Manton Reece that enables you to create collections of tweets for future reference. As I detailed in the article, Storify integration in Tweet Library means you can easily collect tweets from a variety of sources (people you follow, Twitter lists, favorite tweets — Tweet Library does a great job at breaking up Twitter sections in neatly organized “sources” panels) and publish them online as a bundle on Storify. The first official Storify iPad app, however, brings the full feature set of Storify (or at least the majority of its online functionalities) to the tablet, mirroring the web counterpart available at storify.com to allow you to create visually rich social stories that go beyond collecting data from Twitter.

I have been able to test Storify for iPad in the past weeks, using it to create and edit stories that I’ve embedded on MacStories such as this one, or this one. When I first talked to Storify CEO Xavier Damman about their upcoming iPad client, I wondered how well the team had managed to port the desktop user interface and experience of Storify, which is largely based on drag & drop, to the iPad. Furthermore, the Storify web app benefits from the desktop nature of the web browser, which makes it easy to switch between dozens of tabs, collect links, snippets of text, and images, or simply open links from other applications without having to worry about “switching back” using a multitasking tray, such as the one we have on iOS. These are all problems a native iPad app should somehow address, I thought, as it’s not just as easy and quick to switch between the browser and multiple sources on an iPad, and I wouldn’t want the Storify creation process to become slow or, worse, cumbersome. It turns out, the Storify team solved the problem with converting mouse interaction to multitouch, and quite beautifully. (more…)

I have been a heavy user of Twitter for Mac since it was first released over a year ago. While certainly not perfect, for me, it is the gold standard of desktop Twitter apps. As such, it is impossible for me to be objective when reviewing a new client, as I will inevitably end up comparing it to Twitter for Mac (hereafter Twitter.app), so I’m telling you here and now that I didn’t even try to do otherwise. As a result, much of this review consists of comparisons between Osfoora and Twitter.app, and the best I can hope for is that other long-time Twitter.app users find it useful. So let’s get into it. (more…)

The last time I wrote about Twitter clients, I noted how I’d rather settle with a single app for power users, and have other developers innovate on top of Twitter and the technologies offered by Apple to provide a unique take on the standard Twitter experience. Unfortunately, until today very few developers seem to have believed in the market potential for innovative Twitter clients that go beyond refreshing your timeline and catching DMs, with Riverfold Software’s Tweet Library being the best example of what’s possible to do by leveraging the Twitter API, focusing on another kind of experience.

I initially reviewed Tweet Library when it hit version 1.0 on iPad. I wrote:

Tweet Library is a searchable local archive of your Twitter activity, with promising online functionalities that show good room for improvement. At $9.99 in the App Store it might not be an app for everyone, but if Twitter curation is your thing, this is the best you can have on the iPad right now.

Released earlier today, Tweet Library 2.0 offers some fantastic improvements for those who began using the app on the iPad last year, adding a completely new iPhone interface as part of the free, universal update that will have Twitter curation nerds drooling in new functionalities. (more…)

Justin Williams writes about the current state of Twitter clients for iOS:

What iOS needs is the Twitter equivalent to Adium: a well maintained, open source Twitter client that is targeted at the most hardcore and passionate users of both Twitter and the iOS platform.

That, of course, is easier typed than done. Many open source projects fail because of lack of vision or direction. Others fail because they are just badly engineered software that aims to shove every pet feature into a unified product. Projects like Adium succeed because there is an established hierarchy of managers, developers and contributors. Each release has a focus and direction much like a commercially produced project.

My first Twitter client was Twittelator Pro by Andrew Stone, which I installed soon after I got my first iPhone in 2008. After that, I switched to Twitterrific, which I kept until Tweetie came out. For a few months I bounced back and forth between Tweetie, Twitterrific and Birdfeed but, eventually, I settled with Tweetie 2. I loved Tweetie 2. It was the perfect Twitter client for my needs, it was fast and Loren was (is) a great guy. But then Twitter bought the app, started doing all kinds of crazy things to it, and the excitement wore off. I went back to Twitterrific, but it wasn’t the same — I had become very accustomed to Tweetie (now Twitter for iPhone) and the simplicity of Twitterrific was disorienting. Like Justin, I’ve always had a problem with inline DMs in Twitterrific.

Throughout 2010 and 2011 there’s also been a period when I went back to trying every Twitter client out there, including Twittelator Pro (again), but also Echofon, Tweetings, HootSuite, Osfoora, TweetList and TweetLogix. I was addicted to trying Twitter clients until Tweetbot came out and, as I wrote in my review, proved to be a Twitter app for iPhone I could once again fall in love with. I’ve been using Tweetbot for iPhone ever since, and the app keeps getting better on each release. Personally, I don’t agree with Justin’s point that Tweetbot is ”the best designed Android app available for iOS”, but this isn’t the main problem.

The real issue is that these days iOS Twitter nerds are left with Tweetbot and nothing else. Twitterrific clearly isn’t targeting power users — maybe a better expression would be “users that don’t just casually check on Twitter” — and Twitter for iPhone, well, let’s just say it’s not exactly focused on Twitter geeks anymore. How about the other clients? I see very few innovators around, and the only third-party app I’m excited about (again, except Tweetbot, which I use every day) is Twittelator Neue — Stone’s app has a good chance to reinvent a few things especially if it ever comes to the iPad. But looking at the whole Twitter software landscape today, it’s clear to me there isn’t the kind of verve and anticipation for new clients that we experienced three years ago, with developers constantly updating their clients, one-upping competitors in terms of features, and teasing new products that (sadly) never came to be.

In a scenario where the less popular Twitter clients are either a) maintained through bug fix releases or b) updated with minor features every once in a while, lacking major additions like iPad and Mac counterparts, I see a glimmer of hope in Tweetbot — Tapbots are always up to some great stuff — and services like Tweet Marker: available for free to developers to implement in their apps, Tweet Marker is the first step towards that kind of client-side unification whose lack made switching Twitter clients on a daily (or even hourly) basis so painful in 2009. Check out the apps that already support Tweet Marker, and note how they’re the same names that I’ve mentioned above.

Building an Adium-like model for the ultimate Twitter client might be a viable plan, albeit an elaborate one considering all the technical complexities and frequent changes behind the Twitter API. An ideal modern Twitter client for power users should have delightful and powerful iOS apps and an outstanding Mac client that makes it extremely easy to switch environments without user fatigue; you have to make sure the apps are always brought up to date with the latest Twitter features from Twitter itself and iOS 5 (I’m fairly sure the technologies and APIs behind AIM aren’t updated nearly as often as Apple releases new iOS betas), and when everything’s distributed for free you have to make sure you’ve got a dedicated, kick-ass team of contributors and leaders, or things start to get messy (and slow) because of updates, user support, feature request, and so forth.

So here’s another possible scenario. Let’s continue to diversify the offer of available Twitter clients, and settle with one app for power users. Justin doesn’t like Tweetbot, but perhaps one year from now Tweetbot will be available on more platforms with changes and tweaks that everyone will like and use on a daily basis, even Justin. Around that Twitter client for power users, I imagine a flourishing ecosystem of innovative Twitter apps that don’t simply focus on building an alternative to Tweetbot — a daunting task at this point — but provide a unique experience that can live alongside the main, full-featured client. I’m thinking Tweet Library, also by Tweet Marker’s Manton Reece: instead of just focusing on being the perfect regular client, Tweet Library’s built-in client is functional to the app’s real feature: curating tweets and archiving them. This is the path I believe developers should strongly consider for building Twitter-connected apps: focus on APIs, services and interactions with other software. Where’s the Twitter app that integrates with Evernote and lets you annotate tweets? Where is the app to run, manage and archive online polls exclusively via Twitter? Where’s the service that lets you use your custom vanity URL and get beautiful, real-time, reliable click analytics instead of the ugly mess that’s HootSuite?

You see where I’m getting at — I believe developers are (obviously) completely free of investing their time and resources into competing with Tweetbot, but on the other hand I don’t think focusing on other aspects of Twitter means admitting defeat. It’s easy to say “Tweetbot won” or “Twitterrific is the best” when, really, the story is much more complex than that and also goes back to a company that has shown a “peculiar” approach to guiding its own third-party developers.

Will we ever go back to the Birdfeed and Tweetie era? I don’t think so. Twitter is now integrated in iOS 5 and seeing massive growth because of it, thus justifying the prospect of creating an app “for power users” even less. Yet I can’t help but think about a time, not too distant from now, when the power users will finally settle on a single solution for their power-hungry needs, and let other developers innovate atop of the Twitter platform in disruptive new ways. The ideas, devices, APIs and users are waiting.

[Photo by Jorge Quinteros]

TweetDeck has always been looked up to as the power-user’s go-to Twitter app thanks to a huge feature set, its multi-column layout, quick filtering, and its availability across platforms thanks to Adobe Air. When Twitter acquired TweetDeck back in May, many questioned whether Twitter would continue to maintain the client, and whether Twitter would rebrand the app to better fit into their ecosystem. Yesterday, TweetDeck launched natively on Mac and Windows, bringing with it a brand new experience in-line with #NewNewTwitter’s focus. Like Twitter, it’s another big change many will have a hard time adjusting to.

(more…)

That gorgeous app up above? That’s the next-generation Twitter app. Twitter 4.0 melds Twitter’s brand new web experience with your mobile phone, making it easier to discover and share information that matters most to you. Conversations, your activity feed, stories and trends have now been given focus in four new tabs that make Twitter more accessible than ever before.

(more…)

In late September Mozilla released version 7 of its Firefox browser, and as part of the company’s new fast release cycle we noted a few days after the release that a beta of Firefox 8 had already been seeded to developers. In the article, we noted Mozilla promised Firefox 8 would deliver better tab management, deeper Twitter integration, and new features for web developers.

Uploaded to the company’s FTP servers a few days ago, Firefox 8 has been officially released today, with a blog post from Mozilla outlining the differences from the previous version. As with the Firefox 8 beta, Firefox 8 final comes with an option in the Preferences to load existing tabs (the pages you left open the last time you quit the browser) only when they’re selected. This should improve the browser’s startup times, as it’s no longer forced to reload all tabs upon launch.

Another minor new feature is the addition of a Twitter icon in the app’s search box. Mozilla says “Twitter search is currently available in English, Portuguese, Slovenian and Japanese versions of Firefox”, and the new options basically just loads a new Twitter search page for anything you type in the search field — don’t expect Firefox to smartly recognize @usernames or #hashtags, and open Twitter profiles or hashtag pages instead of plain search.

Alongside better handling of third-party add-ons, security and stability fixes, Firefox 8 introduces a series of improvements for web developers:

Improved performance and memory handling when using <audio> and <video> elements

• Added CORS support for cross-domain textures in WebGL
• Added support for HTML5 context menus
• Added support for insertAdjacentHTML
• Improved CSS hyphen support for many languages
• Improved WebSocket support

As far as Lion support goes, whereas Google updated Chrome to take advantage of the OS’ new native scrolling and full-screen mode, Mozilla’s browser still lacks any sort of Lion integration and support for new functionalities.

To read more about Firefox 8′s new features, head over Mozilla’s blog post on the update. Expect a beta of Firefox 9 to become publicly available soon; you can download Firefox 8 from Mozilla’s website here.

With iOS 5, Apple is officially acknowledging the existence of external social networks besides Ping and Apple ID (one of the authentication options for iOS 5′s iMessage) and the result is direct Twitter support, unveiled after much speculation at the WWDC in June, and now available inside Apple’s Settings app. Twitter integration in iOS 5, however, goes beyond a couple of preferences and options to tweak — it’s a systemwide framework that will allow developers to build “official” Twitter support in their apps, as well as let users forget about having to log in with Twitter every time they want to try a new Twitter app.

Twitter is expecting a massive growth in the upcoming months thanks to integration with Apple’s devices, and rightfully so: with the new Twitter preference panel available in iOS 5′s Settings, users are able to sign in once with their Twitter account, and use that “single sign-on” to authorize other apps downloaded from the App Store to access their Twitter credentials. With this method, not only is Apple giving users support for Twitter at a system level, they’re also leveraging iOS technologies to make the experience of downloading and configuring Twitter apps (admittedly, quite many) as frictionless as possible. (more…)

Twitter released an update to its official iOS client today, adding an improved sign up experience, integration with Twitter’s own picture service, and a redesigned Direct Message view on the iPad. As we detailed with our coverage of Tweetbot 1.7 earlier today, iOS 5 is now allowing developers of Twitter-enabled apps to fetch account credentials directly from the iOS Settings app, rather than forcing users to re-authenticate with their accounts every single time. The official Twitter client, as we expected, implemented iOS 5′s single sign-on to allow users to get already-configured accounts from the Settings. The feature is optional and new accounts can still be added manually, but as I wrote with the Tweetbot update, it’s very convenient to be able to add accounts without entering usernames and passwords anymore.

Also new in Twitter 3.5 is direct upload of photos to Twitter’s photo sharing service, available at pic.twitter.com. This can be configured in Twitter’s Preferences both on the iPhone and iPad. What’s new to the iPad is a much improved Direct Messages interface, which has been updated to order DMs chronologically and by thread with a new clean design. Gone is the DM popover from the app’s sidebar, too. iPad owners can now also tap on a location to show tweets nearby.

Twitter 3.5 is available on the App Store now.