Contextually Aware Content Part 2

In my last post, we consider "Mobile" with SDL Tridion. The mobile part, if you're just thinking of screen sizes and a few devices is relatively easy--companies everywhere are addressing it with a mix of content strategy, mobile apps, responsive design. But let's look at some use cases to expand our thoughts, giggle, and cringe at what mobile means to some hypothetical customers.

Consider Use Cases Beyond Mobile

Here are some hypothetical, contextual content use cases that might be plausible for your end users in the near future.
  • Content users want to share or experience with the person next they're next to either by showing them or letting their device and apps communicate (well you can already share pictures with certain phones and video games recognize multiple players)
  • Content users don’t want others to know they're enjoying in places they shouldn't be enjoying them in
    "Hey, no peeking!"

  • Content about an application as they're trying to learn it, and the experiences of others trying to do the same in the context of the software. Think video game in-context, configurable on-boarding "tutorial."
  • Content for "Generation 2020" users expect TV screens and museum signs to be “touch-friendly” -- ("back in my day, we had signs and posters!")
  • Content for users that get upset that you messed with their Netflix stream by watching something on the same account on another device
    someecards.com - Sorry we're blowing up your Netflix queue with inane children's programming.
  • Content that warns users they're doing something dangerous before they commit said dangerous activity (and the option to ignore such danger)
  • Content users think they own and control, but might possibly be influenced by companies (with repercussions)
  • Content possibly aggregated from other sources and displayed in a non-typical interface (a light bulb instead of a dashboard, a floor-to-ceiling touch screen or wall-to-wall touch floor, or maybe even through a smell... wait let me confirm if generated smells are plausible... yep!)
What's needed here is content, application, and "experience" design. Content-producing companies (aren't we all?) need to craft flexible experiences across more and more screen sizes and eventually multiple interaction methods.

We conclude in part 3.


No comments:

Post a Comment

Feel free to share your thoughts below.

Some HTML allowed including links such as: <a href="link">link text</a>.