Design  |  Ahalogy Mobile

Project details

  • Ahalogy,  Spring 2014
  • 39° 7′ 43.2696″ N, 84° 25′ 50.7756″ W

Contributed to

  • Product definition
  • Interaction patterns
  • Visual design
  • UI development


Before there were Instant Articles, there was Ahalogy Mobile. For a while anyway.

Ahalogy Mobile was a product designed and built for publishers to improve the reading experience of their sites when viewed within a mobile in-app browser. I worked on the system architecture, designed it and contributed to its development.

The rub

Ahalogy works with big consumer brands and high-end independent publishers, helping them spot trends, produce useful stories, and publish those effectively on Pinterest and elsewhere.

We started realizing our customers’ upside was being capped by the user experience of the pages to which the Pins linked.

Too often, tapping a Pin from Pinterest’s mobile app would fire up a UIWebView (back before we had SFSafariViewController), inside of which you had the slow, ad-laden, painful privilege of viewing the recipe, look, or article.

These are typical of what many Pins lead to

These smart but small publishers were still struggling with adapting to the new realities of socially discovered content. Their sites were often still unresponsive, high latency, and poorly organized.

Back then I wrote more about this problem if it tickles your fancy.

The design

This was before Google AMP or anything like it. So we had to build it ourselves.

The design began, of course, with how it worked. We needed to control the presentation of contents across thousands of sites on multiple versions of Wordpress, only on certain devices and from specific referrers, all without changing the sites' actual themes in any way.

The creators inserted our javascript snippet which, when identifying inbound traffic from Pinterest on a mobile device, would stop the DOM from loading and display the same content from our server. We stored parsed copies of all their old and newly created posts, and made those available from a CDN. That way we could load significantly faster, control the interface for reading, asynchronously insert the right ad at the right point in the article, and recommended the perfect article to read next from any of the publishers in our content network.

The interface design was based on a card stack structure. We used the semantics of the post to organize it into multiple cards which the reader could scroll and flip through (A few paragraphs, an image and its caption, a list of ingredients are examples of individual cards).

The result was a faster, cleaner user experience we could easily distribute to all of our partner sites. Time on site increased by 30–100%. And because the experience was so unique and the single sponsorship per post so engaging (without turning the experience sour), we were selling to top advertisers at a premium CPM. That gets us paid and enables the publishers to build their businesses. It was a win for all involved: readers, publishers, and advertisers.

The premature demise

The reason I haven't linked out to any live examples, dear reader, is that the product met its demise mere months after launch. Ahalogy had to pull it from the market because of what we'll call some strategic bullying by another company.

The end notwithstanding, Ahalogy Mobile showed me there’s still innovation left to be done in the rebundling of digital publishers. Perhaps it will be Google’s AMP which solves some of these problems for the myriad small but influential blogs. Or it will be the native platforms themselves like Facebook Instant Articles and whatever Pinterest does with their Instapaper acquisition. As long as someone does something.  

Other projects