Mobile CMS Has Arrived!

Mobile CMS Has Arrived

Sitefinity 6.0Telerik

Gabe Sumner

Telerik | Sitefinity CMS

@gabesumner

This webinar will answer two questions:

WHY does CMS need to address mobile?

HOW can CMS address mobile?

WHY does CMS need to address

mobile?

Mobile is on course to overtake desktops

2009 2015E

2,000

1,600

1,200

800

400

This is clearly reflected in today’s headlines

And the “payoff” is becoming evident

Numerous businesses are enjoying the benefits of mobile engagement.

And we’re working out the “kinks”

* Source Foresee

Mobile experiences are nearly on par with desktop

However, look more closely…

Only the top online retailers are reporting these results

Other “top” websites paint a different picture

* Source Top 500 Guide – InternetRetailer.com

In fact, evidence suggests many of us are struggling

* Source Strangeloop

* Source Econsultancy

The Tale of Two Cities…

The opportunity is real.

The path to success is explored.

But many are struggling.

Why?(The answer is complicated, but lack of tooling is hurting us.)

CMS isn’t helping with Mobile

We’re still climbing the adoption curve

We are here. And tools historically help bridge

this gap.

CMS needs do more than “talk” about mobile

Lack of tooling has resurrected the “webmaster”

Your Idea

DeveloperExecution

(Everything related to mobile must go through a “technology” gatekeeper)

HOW can CMS address mobile?

Responsive

Website

Mobile AppMobile Website

Device-Agnostic Experience

Device-SpecificExperience

There are three mobile strategies to

choose from

(Each has pros/cons and there are reasons to combine

strategies)

Responsive

Website

Responsive Grids

CSS3 Media Queries

Mobile App

HTML5 Mobile Apps

Cloud Services

Mobile Website

Device Detection

Device Redirection

Device-Agnostic Experience

Device-SpecificExperience

And behind each strategy are numerous technologies

CMS must evolve to help create & manage these

technologies

How can CMS address Responsive Websites?

One website that adapts to ALL devices.

Responsive Websites adapt to any screen

This technique is based on adaptive grids

This allows 2-columns to become 2-rows for small screens

And there are numerous frameworks for this task

However, these frameworks exist

outside the scope of the CMS

Instead, these grids should be infused into the WCM

This makes the WCM aware of content AND layouts

These layouts can then be adapted for different devices

Once the WCM is aware of the layouts, it can act on this information

Transformations can happen at a site-level or page-level

This enables different pages (or sections) of the website to transform differently.

Or hidden from specific devices

All of this is happening in the CMS, not in source code

And previews create awareness of the result

This gives content creators context about the mobile experience being created.

Responsive

Website

Mobile AppMobile Website

Device-Agnostic Experience

Device-SpecificExperience

There are three mobile strategies to

choose from

(Each has pros/cons and there are reasons to combine

strategies)

How can CMS address Mobile Websites?

Specially prepared website for specific devices.

Specialized experiences for specific devices

(Desktop Experience) (Smartphone Experience)

Device Detection & Redirection

Redirect specific devices to a specially prepared website

Browse the entire website using a mobile simulator

This allows the overall mobile experience to be tested in a variety of devices.

Responsive

Website

Mobile AppMobile Website

Device-Agnostic Experience

Device-SpecificExperience

There are three mobile strategies to

choose from

(Each has pros/cons and there are reasons to combine

strategies)

How can CMS address Mobile Apps?

Deployable to mobile app stores

Mobile Apps fetch data through Web Services

This “structured content” becomes accessible through a RESTFUL Web API’s

These data types should be established in the CMS

And the WCM should automatically generate Web API’s for accessing this data

Mobile Apps can then be generated for this data

Scaffold a CRUD-style Mobile App based on CMS-managed Content Types

Cloud Synchronization should be “built in”

Mobile Apps interact with cloud services instead of on-premise infrastructure

Cloud Services

Publish once to everywhere

Responsive

Website

Device Preview

Device Simulator

Layout

Transformations

Hidden Layouts

Mobile App

Module Builder

Hybrid App Builder

Development

Environment

Cloud Integration

Mobile Website

Device Preview

Device Simulator

Device Detection

Site Redirection

Device-Agnostic Experience

Device-SpecificExperience

How can CMS address mobile?

Try it for yourself atwww.sitefinity.com/try

Sitefinity CMS

Telerik

Or contact us for a live demo at sales@sitefinity.com