A few years back, when we first decided to embark on what has become Remarkable, we immediately envisioned a solution to the problem of updating content to native mobile, tablet, and wearable apps - platforms in critical need of an easy, non-technical solution for content update and 'injection'. The issues were obvious, and the process of making simple updates to a native app was simply broken and non-existent.
Following our 'soft launch' in April 2014, Remarkable quickly garnered significant industry attention as the first CMS truly built for the mobile and wearable age. And a number of major media companies and many of our key clients quickly jumped on board, discovering a totally new (and simple) way to manage content in their mobile and tablet apps.
Fast-forward to 2015 and the number of 'Enterprise' customers continues to grow, while we've been flooded with early adopters and first-time users jumping on our 'Simple' Tier and trying Remarkable out for themselves - integrating the Remarkable SDK into their iOS and Android Apps.
And while Remarkable has indeed been fulfilling its promise as the first CMS built for the Mobile and App economy - our clients and new customers are increasingly utilising Remarkable to manage their Web sites and Web App instances.
In fact, the number of Remarkable instances and uses in traditional Web sites and Web Apps has simply exploded in the past year - in many cases becoming our most popular delivery channel.
In truth, it really comes as no surprise as Remarkable was built from the ground up to manage content in small bite-sized cards (or chunks) - allowing developers and editors to 'build' full Web pages from the smallest of assets. The ability to move away from the locked/rigid template-based approaches of other Web CMS tools (Wordpress, Drupal, Sitecore, etc) has meant a totally new approach to Web development - one that clearly owes its inspiration to the requirements of smaller screen native Apps. So in a sense, this evolution has come full circle - as the demands of the smaller apps have informed our approach to the larger, PC pages.
If we look at the typical path of content strategy and planning - it has always followed a 'cascade' approach, with content being initially planned in locked Web-page based templates and then being (ruthlessly) squeezed, clipped, pruned and honed for smaller devices:
This process has not only led to the expected sloppy result for smaller devices (like native mobile apps and wearables) - but has also produced a totally locked and shackled page construction for the original PC pages themselves.
In essence, there is no flexibility, no movement, and no ability to react to changing content requirements.
What Remarkable has allowed is a total reversal of the 'cascade' from PC to Mobile - meaning the demands of the smaller, more agile content cards found in mobile and tablet apps is inherited back to the original Web pages themselves:
This data-driven content approach has helped many of our customers (from small startups to major media and broadcast organisations) break free of the page and file-based content model - allowing the content of their Web sites to ultimately be more reactive, dynamic, and flexible.
In a way, a Remarkable-driven Web site is simply a collection of content cards - digestible chunks of content which can be redeployed to any number of channels (including various positions and places within the Web site itself).
We're thrilled with how Remarkable has informed and guided an entirely new way to manage Web content. We'll always have our focus firmly toward the future, but for many of our customers, Remarkable has enabled an exciting and thoughtful approach to next generation content management for every digital channel - from the smallest Apple Watch App to the largest database-driven Web site.
And that's really what the Remarkable revolution is all about.