Mesh networking, the Internet of Things, Pervasive Computing – let’s build the future now!

Mesh networking, the Internet of Things (IoT), pervasive computing – these are all threads in the fabric of our everyday (near future) lives.

gold-metal-mesh

Google provides superb machine-learning. Apple contributes gorgeous devices and (relatively) seamless user-centric experiences. Companies like Dropbox, Amazon and, intriguingly, Upthere offer unlimited, always-available storage.

But we don’t yet have the software or the infrastructure that knits everything together.

This is such a thrilling time to be working toward building interoperable, cohesive, compelling experiences for myself, my friends, my family, my community.

Let’s go!

 

Mesh networking, the Internet of Things, Pervasive Computing – let’s build the future now!

Bridge the gap between web & app: Google App Indexing & Apple Universal Links

Discoverability – by users and by search engines – frustrates anyone who aspires to make consumer products.

The bog-standard SEO consultant will point to a variety of Google-specific remedies and leave it there. And really, the best baseline SEO advice is found at Moz Blog. But if we define “search engine optimisation” broadly, there is so much more to SEO than fiddling with Google Webmaster Tools.

When evaluating the SEO-ness of a suite of products, the guiding questions to be answered first are :

  • How do customers find us?
  • Who are the gatekeepers between our public and our products?

This article explains how to knit together the three silos of web content, app content and referring links from social media for great SEO visibility and a smooth customer experience.

HOW DID WE GET HERE?

Since the rise of the iPhone in 2007 and the iOS App Store in 2008, mobile handsets have come to dominate how people communicate over the internet. There’s no better, more succinct narrative of this upheaval and democratisation of access than Benedict Evans’s presentation, “Mobile is eating the world“.

The presentation captures the pervasiveness with which mobile dominates our lives and businesses, but it glosses over some of the growing pains we, as digital agencies and brands alike, have suffered in pursuit of the best way to reach the most people on the planet – apps.

It’s helpful to remember the state of the internet 8 years ago. By the end of 2008, Google dominated the major customer acquisition channels of the time – search and advertising.

One silo - web

But, with the rapid adoption of mobile, people spent an increasing percentage of time on Twitter (without mobile, Twitter would be a footnote in digital history) and, more importantly, Facebook. Freed from the constraints of desktop computing, mobile became an enabling platform for social networks – what better way to kill time or casually keep in touch? The social graph exploded and became Facebook’s most valuable asset.

Two silos - social and web

If you look at the analytics of any publisher in the world, you’ll discover that Facebook dominates “customer acquisition” – e.g., where publishers get customers, usually called “referrers” in analytics suites.

Google and their search/advertising silo on the web has been supplanted in some markets and businesses by links posted by people on Facebook and clicked on by people using Facebook.

At the same time, shifted how they accessed Facebook and Twitter – from a web browser to a native app. That pattern of usage cuts across all digital services – people spend most of their time on mobile using apps and not their web browsers. Because of privacy and security concerns, apps are designed to operate autonomously in another silo, particularly on iOS.

three silos - social, web and apps

If I email a link from a news site to my mum, how can I ensure the link opens in the app on her iPad rather than opening in Safari or in Chrome? How do we break down the walls between silos and streamline the means and methods of customer acquisition? How do we create better customer experiences? By forging links between the silos.

FACEBOOK

This isn’t a new concept. Facebook proposed a “deep links” standard in 2014 http://applinks.org.

Developer documentation – https://developers.facebook.com/docs/applinks/overview

Since I make tightly-integrated products that have breaking news, video on demand and live broadcasting components across the desktop/mobile web, mobile apps and “home devices” apps (TV, Playstation, Xbox), it’s important to clearly define the relationship between content across these platforms – and Facebook’s suggestions simply aren’t a silver bullet. This brings us to the app platform vendors, Google and Apple.

GOOGLE

Not to be outdone or outflanked, Google has a way to securely expose app data to Google Search called App Indexing : https://developers.google.com/app-indexing/ It’s a straightforward solution for Android, but it is in beta on iOS.

Android

  • Add intent filters to your app manifest
  • Connect your app to your website through the Google Play Console and Google Search Console

iOS

  • Declare support for custom URL schemes
  • Handle incoming URLs that use the custom schemes
  • Add a custom URL scheme for App Indexing
  • Add back bar support for Search deep links

Developer documentation :

APPLE

Over the past couple of years, Apple doubled down on privacy and security and so it’s not surprising that they take a dim view of third parties indexing app content.

Apple refer to their scheme as Universal Linkshttps://developer.apple.com/library/prerelease/ios/releasenotes/General/WhatsNewIniOS/Articles/iOS9.html#//apple_ref/doc/uid/TP40016198-DontLinkElementID_2

  • com.apple.developer.associated-domains entitlement to one’s app
  • apple-app-site-association post JSON file to one’s website
  • use Apple-specific (and Schema.org standard) markup to make content mirrored in an app and on the web visible

Great WWDC2015 video on the topic : https://developer.apple.com/videos/wwdc/2015/?id=70

Silos connected with deep link schemes from Google and Apple

Adopting both Google’s App Indexing and Apple’s Universal Links will ensure maximum discoverability across web search and on-device search and guarantee a great app experience for customers on mobile.

Bridge the gap between web & app: Google App Indexing & Apple Universal Links

Part 3 : Survey the competition, see what works and what doesn’t using “jobs to be done”

In Part 1 we began by asking ourselves some guiding questions to challenge our initial assumptions. In Part 2 we defined our vision and mission, products or services and how we’ll know when we have succeeded.

Now we want to survey the competition – see where they are, what they’re doing – and why. A typical competitive analysis methodology :

  • Who are they?
  • Who are our competitor’s users?
  • How does our competition reach their users?
  • What’s the product?
  • What’s the product’s position in the market?

After we’ve done our homework about our competition’s customers and devised a proper SWOT analysis, we will want to know more about how products are used.

Methodology for product development based on a review of the competition and determining the
Methodology for product development based on a review of the competition and determining the “jobs to be done”

At work I recently completed a study of 20 different sport and news websites, in particular the editorial strategy of responsive web views vs app home screens and their respective navigational schemes.

Have a look at following examples of two very similar, yet subtly different products. What conclusions do you draw from the following questions:

  • What are the “jobs to be done” by this product?
  • How do our competitors minimise effort?
  • How do our competitors monetise?

Remember, just because a cool new feature or service exists in a competitor’s product doesn’t mean it’s appropriate for your product.

It’s important to know why a feature exists, because that’s the only way you’ll be able to determine if it’s the right fit for your product and help achieve your commercial goals.

Part 3 : Survey the competition, see what works and what doesn’t using “jobs to be done”

Part 1 : So you want to build a successful and profitable web site, mobile or home devices app, service or platform?

Often when I tell newly met acquaintances how I make my living this statement/question arises – “I have an idea for an app (or website, etc) – tell me how do I make it?” Where to begin? Perhaps with a quick overview of my previous experience. Over the past 14 years I’ve made a wide array of products and services, monetised through advertising, subscription and mixed revenue models :

  • Streaming video portals
  • Screen savers
  • Advertising creatives
  • Flash-based games
  • Marketing microsites
  • Educational assessment
  • Breaking news, live video & video-on-demand sites and apps

Despite differences in scale and diversity, all of these products began by answering a series of “guiding questions”. These aren’t the classic “five whys”, but instead help lay the foundation for further development of your idea or proposition :

  • How would you describe this in 60 seconds?
  • What problem does it solve?
  • What is the service?
  • What is the opportunity?
  • Who are the competition?
  • What is our competitive advantage?
  • How will we monetise this?
  • What is required to deliver this?
  • What don’t we know and how will we find the answers?

If you’re able to quickly answer these questions, you’ll be well on your way toward making a commercially viable product or service.

This will be the first in a series of articles discussing how one conceives of, constructs, delivers and maintains a digital product. It’ll be a blend of commercial considerations, project management, product delivery and technical development.

Continued in Part 2, Part 3.

Part 1 : So you want to build a successful and profitable web site, mobile or home devices app, service or platform?

Facebook ad profit a staggering 1,790% more on iPhone than Android

Nice to quantify the appeal of iOS development for those of us interested in generating revenue from both direct to consumer app sales/in-app purchases and advertising.

Facebook ad profit a staggering 1,790% more on iPhone than Android

Link

Using iOS 6 Maps in the real world: when your solution is the problem

After a week using the new Apple Maps app in iOS 6 around London and on my business trips to Paris, I find it perfectly capable of finding specific addresses, but the information one sees on load lacks context.

Where is Belsize Park tube station? I see Chalk Farm, but not Belsize Park … until one taps in closer. Very odd behaviour, indeed.

Did anyone at Apple use this to navigate through areas with which they were unfamiliar? What does one do when lost or simply in a new place? Look for transportation links, points of interest, a place to eat, have coffee, quaff a cold gin and tonic …

I suspect the fury that greeted the move from a Google-powered dataset to Apple Maps has little to do with aesthetics, but rather the lack of a quick, accurate answer to the question: “where is the [tube/railway station, hotel, Starbucks, Ye Olde Pub] that I think is around here somewhere, but I’m not entirely sure about how to find it]?”

Nice to see there’s a place for coffee, but where’s my hotel – and which metro is that?

Just the other weekend I was going to Paddington for a day out in the Buckinghamshire countryside. I took the 46 bus from Hampstead, but it skirted around the station in a way with which I wasn’t wholly familiar. I opened Maps on my iPhone and … had no idea where Paddington was in relation to my bright blue blip despite being no more than a two-minute walk away.

This highlights precisely why one takes a hell of a lot of care in the creation of user stories and exploring use cases: if your product doesn’t solve a real-world problem for your user, that really is a problem.

Using iOS 6 Maps in the real world: when your solution is the problem

Facebook SDK 3.0 Beta for iOS – Facebook Developers

It’s been clear for several years now, but apps developed for specific devices using OS-specific hooks offer the best user experience. I test so many apps made with seeming contempt for the user – Facebook’s iOS app at the top of the list – and have had so many depressing conversations about developing apps that are little more than UIWebView containers that this announcement from Facebook is a welcome validation of the native app dev strategy.

Facebook SDK 3.0 Beta for iOS – Facebook Developers

Link