<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[The Future Content - Medium]]></title>
        <description><![CDATA[Exploring the future of web content — experiences, content management, CMS, development, and more. - Medium]]></description>
        <link>https://medium.com/the-future-content?source=rss----fc0243622290---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>The Future Content - Medium</title>
            <link>https://medium.com/the-future-content?source=rss----fc0243622290---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:35:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/the-future-content" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Inception CMS]]></title>
            <link>https://medium.com/the-future-content/inception-cms-c316851d73b1?source=rss----fc0243622290---4</link>
            <guid isPermaLink="false">https://medium.com/p/c316851d73b1</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[cms-development]]></category>
            <dc:creator><![CDATA[Christopher Zimmermann]]></dc:creator>
            <pubDate>Sat, 15 Feb 2020 20:29:00 GMT</pubDate>
            <atom:updated>2020-10-02T06:12:26.098Z</atom:updated>
            <content:encoded><![CDATA[<p>What if a CMS could edit itself?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WwJmOm0Gb_qOnWB1DQH-OA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@smnzhu?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Simon Zhu</a> on <a href="https://unsplash.com/s/photos/inception?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>A CMS is a tool, an app, to edit a website.</p><p>It’s interesting that the tool itself <em>is a website</em>.</p><p>And it’s interesting that websites become more app-like.</p><p>OK, there have been “web apps” for years. But an important recent shift is that the app-ness is moving from the backend into the frontend. Back-in-tha-day, the <em>web part</em> of the web app was just a thin UI to communicate with the actual application, which was running on the server. Now, with Vue, React, Angular frameworks and PWAs, the app is really running “on the web”, in your browser. For example, consider any web app with an offline mode — like Google docs.</p><p>(We’ve had “thin clients” back in days of yore — but usually running in other technologies like Java Applets, Flash or other “embeds”. They were only running “on the web”, but were not “of the web” as they are today.)</p><h3>Inception</h3><p>So, if a modern CMS has tooling to assemble not just static web pages, but also more dynamic app behaviours… And if this modern CMS is itself a web app that is running more in the browser and less on the server… then can I use the CMS to edit itself? That’s what I mean by Inception CMS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*W7a9jNvs_2QnZ9yd" /><figcaption>Still from the film Inception, 2010, Warner Brothers. All rights reserved.</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FJvurpf91omw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJvurpf91omw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FJvurpf91omw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f78f22ad6b62d308de26a2102295124e/href">https://medium.com/media/f78f22ad6b62d308de26a2102295124e/href</a></iframe><h3>Chicken and Egg</h3><p>Does that mean I could just build the whole CMS with its own tools?!??</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zX7p_swrMU9i1aT1bI8hBw.jpeg" /><figcaption>M.C. Escher, <em>Drawing Hands</em>. Copyright 2017 The M.C. Escher Company, The Netherlands. All rights reserved. <a href="http://www.mcescher.com/">www.mcescher.com</a></figcaption></figure><p>It’s fun to imagine what would be the simplest, most minimal primitives that you would need to be able to do this. (A button, a view, and a layout?) But that’s really just a thought experiment. Reminds me of all the self-assembly research in robotics that was big 10 years ago.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZD1H70aQc7U%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZD1H70aQc7U&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZD1H70aQc7U%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c88d79515acffa90b47535f3fef0b4b2/href">https://medium.com/media/c88d79515acffa90b47535f3fef0b4b2/href</a></iframe><p>Oh wow. Still going strong — check this out!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhI5UDKaWJOo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhI5UDKaWJOo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhI5UDKaWJOo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3dad4f4ef18b26b787e241d37c39efdd/href">https://medium.com/media/3dad4f4ef18b26b787e241d37c39efdd/href</a></iframe><p>Realistically though I’m picturing a fully functioning CMS with a really good “Page Builder” tool. But now it’s not just editing pages, it’s editing frontend apps (SPA, or “micro-frontends”). Lets call it an <strong>App Editor</strong>. A user can use the App Editor to edit or customise other features of the CMS, like adding a field to an existing form. Or they could assemble and add a new specialised tool to it — for example for choosing products out of an integrated e-commerce system. A CMS that can edit itself.</p><p>The user, the “app author”, can choose from a palette of useful high-level components and place them on layouts to build even higher level units of functionality.</p><h3>Same technology for the CMS &amp; the website</h3><p>That nice theoretical idea relies on the assumption that the CMS is built with the same building blocks as the websites it builds. Usually that is not the case. (For example Magnolia CMS where I work is built with Java but creates websites with HTML or frontend frameworks.) But when it is, it brings another nice advantage: What a developer learns about building websites also applies to building or tuning the CMS itself, and vice versa. I love it when things have this consistency. It’s one of the attractions and advantages of NodeJS, leverage your same javascript knowledge on the client and the server.</p><h3>Today</h3><p>I don’t know of any “Inception CMS” today. At <a href="https://www.magnolia-cms.com/product/headless.html">Magnolia</a> we recently launched a <a href="https://www.magnolia-cms.com/product/single-page-apps-editing.html">Visual SPA Editing </a>feature that goes in the direction of the “App Editor” proposed above. (It lets teams take the headless CMS approach, but still give content authors a WYSIWYG editing experience.) But we don’t yet support using it to edit the Magnolia interface <em>itself</em>. The Inception CMS idea is not an explicit goal for us currently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5OmgXkm-ixxj3rCYiV1Pmw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@joshuafuller?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Joshua Fuller</a> on <a href="https://unsplash.com/s/photos/refraction?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>What about you? Do you think the idea makes sense, or does the story have some gaping “plot holes”? Would a capability like this be practically useful? Do you know of CMS that can do this already — or one that is close?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c316851d73b1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-future-content/inception-cms-c316851d73b1">Inception CMS</a> was originally published in <a href="https://medium.com/the-future-content">The Future Content</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hybrid Headless]]></title>
            <link>https://medium.com/the-future-content/hybrid-headless-a280209d1e3f?source=rss----fc0243622290---4</link>
            <guid isPermaLink="false">https://medium.com/p/a280209d1e3f</guid>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[headless]]></category>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[digital-experience]]></category>
            <dc:creator><![CDATA[Christopher Zimmermann]]></dc:creator>
            <pubDate>Mon, 20 Nov 2017 13:11:52 GMT</pubDate>
            <atom:updated>2017-11-21T09:31:50.358Z</atom:updated>
            <content:encoded><![CDATA[<p>Hybrid headless is a fancy name for a simple concept: use a full CMS which also serves its content directly via REST API, and manages clean, presentation-independent content. In this article, I’ll share four key hybrid headless techniques. All of these techniques revolve around the interplay of the delivery of content via REST of a headless CMS, plus the full-featured UX of a full CMS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wfFpWO1cNX80hLo1.png" /></figure><p>The headless CMS approach is great for so many reasons. Decoupling content from presentation ftw! Innovate with mobile apps and the new crop of front-end frameworks! Get started instantly! But with headless, there are <a href="http://www.cmswire.com/web-cms/a-headless-cms-wont-solve-all-your-woes/">some limitations</a> that could <a href="https://dri.es/drupal-is-api-first-not-api-only">bog your project down</a> a little down the road.</p><p>These are the two key issues for me:</p><ol><li>Marketers and content creators (users who aren’t developers) cannot do as much.</li><li>A headless CMS simply doesn’t cover many of the common content management requirements.</li></ol><p>But this isn’t a “headless CMS are bad” article. I just want to set the stage for hybrid headless, in order to highlight some of the benefits of this approach.</p><p>You’ll have to balance the pros and cons for your project. Maybe these limitations are not relevant to your project, or are outweighed by the benefits of going totally headless.</p><p>Let’s take a look.</p><h3>The UX of a full CMS</h3><p>What’s so great about this UX? It empowers non-developers to perform key website tasks themselves. Of course all CMS are different, but there are two tools that are shared by most full CMS in some form:</p><p><strong>The page tree</strong> (aka site map or content tree)</p><p>You can see and manipulate the structure of your entire project, typically represented as a hierarchy with the homepage at the top.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Anj3mf9GEHGuCKbo.jpg" /><figcaption>The page tree</figcaption></figure><p><strong>The page editor</strong> (aka page builder, WYSIWYG editor, post editor)</p><p>You can build and edit a page — choose a template for the page, modify its layout, drag-and-drop components, and populate it with content stored in your CMS. While it’s still called a “page editor”, a better term in this day and age is “experience editor” — it’s where you can really build an experience, not just enter content data in a form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y_pl1gj6luGKMN_W.jpg" /><figcaption>The page editor</figcaption></figure><h3>The four key hybrid headless techniques</h3><h4>Full CMS and REST API</h4><p>Create clean, presentation-independent content. Serve the content through a website managed via the page tree and page editor, <strong>and</strong> serve it through REST endpoints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*A0kJSyZRFHf2pD5r.jpg" /></figure><p>Driven by the popularity of mobile apps, front-end js frameworks and SOA, many companies already use this fundamental technique. Marketers and content creators are self-sufficient and have full freedom to create and manage the website. Meanwhile, with the REST API, developers can create mobile and front-end apps in their programming languages and frameworks of choice — or pipe the content through existing delivery pipelines or third-party systems.</p><h4>Page fragments as JSON</h4><p>Marketers use the page editor to curate a <em>fragment</em> of a page with content and specific templates. Developers pull just the pure content of that fragment, as JSON, and render it in their app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HyqO11of3jSm6R1n.jpg" /></figure><p>The benefit of this approach is that marketers can arrange not just their website, but also experiences that are used in apps and other systems. And they can do it in familiar tools, potentially including the ability to use the personalizaton and targeting features of the CMS.</p><p>Since developers pull content directly as JSON, they can use it however they want in a headless fashion. Developers have control over the actual display of the content, so it might look different than in the page editor.</p><p>At Magnolia, we have a banking client who uses this approach to enable their marketing team to update campaigns that are displayed in the consumer banking application. That banking application is delivered from a different server and vendor. This gives the marketing team the power to push new campaigns whenever they need to, independent of the lifecycle of the banking app itself.</p><h4>Page fragments as HTML</h4><p>As above, marketers use the page editor to curate a fragment of a page with content and specific templates. The developer configures another system or app to pull that fragment, rendered by the CMS as HTML. This is similar to the previous technique, but delivers rendered HTML instead of JSON.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2wIQIrxyoax0hLW9.jpg" /></figure><p>“Wait, wait, what about a REST API? What about presentation-independent content?” you say. You caught me! It’s relevant in this list because it’s still about another app or delivery system grabbing some content from the CMS.</p><p>As before, the marketer creates experiences that are used in apps and other systems, with familiar tools. In this technique, since rendered HTML is delivered, the marketer also has a WYSIWYG authoring experience with live preview of the content.</p><p>At Magnolia, we have a number of customers who have chosen this approach for their web properties — such as e-commerce retailers whose marketing team wants to hand-craft the marketing content for the various departments of their shop with the page editor. The e-commerce system pulls these HTML fragments from the CMS to spice up the important, but dry, product data stored in the e-commerce system.</p><h4>Build front-end apps</h4><p>Developers design their front-end apps with a modern component-based architecture. Marketers use the page editor to manage the content of, configure, and assemble front-end javascript apps (aka SPA).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7cwjM_yPVd_Kzpb8.jpg" /></figure><p>The first three techniques can all be used to manage the content of front-end apps (among other things). This one goes further.</p><p>With this approach, marketers can actually build a front-end app — in the same way that they are used to building a web page today.</p><p>This is huge since there is such momentum with frameworks like React, Angular and Vue. We have a lot of customers who love these frameworks, but are struggling with how to give their non-technical staff a way to manage them — so that the devs are not always burdened making tweaks and doing new releases whenever there is a change required.</p><p>In this technique, the “page editor” becomes an app editor. Marketing teams can build the apps that they need in a WYSIWYG environment and work with a live preview of the end-user’s experience.</p><p>The javascript frameworks all support this technique — but developers must take some care to create such dynamic apps that can be changed on-the-fly. The key difference is that instead of the app “hard-coding” exactly which components are nested within a parent component, it rather specifies a list of the components it <em>could</em> contain. When the app initializes, it loads a JSON configuration file that defines which components should actually be instantiated at each location.</p><p>There are aleady some nice libraries out there that make this easier, such as <a href="https://github.com/DeloitteDigitalAPAC/react-habitat">React Habitat</a> from Deloitte.</p><p>At Magnolia, we are working on a generic solution which we plan to open source soon.</p><h3>Hybrid headless in practice</h3><p>It’s probably helpful to get concrete and see how those techniques can be applied in practice. As a product manager at <a href="https://www.magnolia-cms.com/">Magnolia</a>, I can draw from my knowledge of that CMS. (And maybe pique your curiosity about it too. :) The four techniques in practice:</p><p><strong>Full CMS and REST API</strong></p><p>Content apps provide a form-based editor for structured (presentation-independent) content. Content apps are equivalent to the editors in pure headless CMS.</p><p>Stories app provides a rich “medium-esque” editor for long-form content, giving the author freedom to create a full story instead of just fill in a form. Content is stored in clean blocks for retrieval as JSON via REST.</p><p>Content can be easily retrieved as JSON. Developers can quickly configure endpoints in a few lines of YAML. Access can be controlled through a full-featured role-based security system.</p><p><strong>Page fragments as JSON</strong></p><p>There are two ways to get the content of a page fragment via JSON.</p><ol><li>The REST API can return a fragment from within a page, a complete page, or a collection of pages.</li><li>Render variations: Any template can provide multiple rendering variations, one of those can return JSON. A developer must code the JSON response using standard templating practices. The jsonfn library can be used to return the full content in one line of code. This approach can be used if the format of the REST API response is not the exact one you require.</li></ol><p><strong>Page fragments as HTML</strong></p><p>In Magnolia, a feature called “Direct Component Rendering” gives easy access to any fragment of a page simply by including the “address” of the fragment in the url.</p><p>For example, to access a fragment on this page: <a href="http://demopublic.magnolia-cms.com/about.html">http://demopublic.magnolia-cms.com/about.html</a></p><p>You can simply add “/main/00” to grab the first element of the “main” area. Try: <a href="https://demopublic.magnolia-cms.com/about/main/00.html">https://demopublic.magnolia-cms.com/about/main/00.html</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/0*M9HhgIR5JrMiNYtY.jpg" /></figure><p><strong>Build front-end apps</strong></p><p>The Magnolia page editor uses simple HTML comments on the page to configure and indicate where the WYSIWYG editing widgets should be displayed. These invisible comment blocks provide information such as which areas of the page are editable, and which components can be inserted in that area.</p><p>With a little javascript code, these HTML comments can just as easily be inserted in the HTML generated by front-end javascript frameworks. This makes it easy to make front-end apps editable in Magnolia. I assume a similar mechanism is used in other CMS page editors, and so that the general approach will be do-able in other CMS as well.</p><h3>Conclusion</h3><p>Over the past 15 years, the pendulum has swung back and forth in favor of strict separation between content and presentation. At one extreme: only entering content in database-like forms is allowed, putting a wall separating authors from their readers. At the other: all content entry in-place in a WYSIWIG editor with the attendent risks of breaking the design.</p><p>But now I see a nice opportunity with the hybrid headless approach to become more subtle, less extreme, and take the aspects from both which really help people get their jobs done.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a280209d1e3f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-future-content/hybrid-headless-a280209d1e3f">Hybrid Headless</a> was originally published in <a href="https://medium.com/the-future-content">The Future Content</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Apple’s new ARkit, it’s a much bigger deal than you think.]]></title>
            <link>https://medium.com/the-future-content/apples-new-arkit-it-s-a-much-bigger-deal-than-you-think-39faefd70e9a?source=rss----fc0243622290---4</link>
            <guid isPermaLink="false">https://medium.com/p/39faefd70e9a</guid>
            <category><![CDATA[augmented-reality]]></category>
            <category><![CDATA[virtual-reality]]></category>
            <category><![CDATA[mixed-reality]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[content-management-system]]></category>
            <dc:creator><![CDATA[Christopher Zimmermann]]></dc:creator>
            <pubDate>Tue, 12 Sep 2017 12:12:33 GMT</pubDate>
            <atom:updated>2017-09-12T12:12:33.305Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yqFCsp_jZDhQniD_rvv69A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/9dD0gFvrFnY?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Yoann Boyer</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I know I’m not going out <em>too far</em> on a limb if I say that Apple is about to do something big. They are releasing ARkit in their imminent iOS 11 launch. But the thing is, despite all the hype about VR &amp; AR — most people think it’s just the latest tech gimmick or something for “the gamers”. Most people don’t yet know that the world is about to change.</p><p><strong>Info:</strong> <em>Augmented Reality (AR) also known as Mixed Reality (MR), is where computer generated images and sound are mixed or overlaid on our normal experience of reality. Imagine wearing glasses that let you see the real world, mixed with digital imagery, for example a green line guiding you to your destination.</em></p><p>Apple is not launching “AR glasses”. In the version Apple is launching (with <a href="https://developer.apple.com/arkit/">ARkit</a>) you simply look at the world through your phone and this view is digitally augmented. This “handheld AR” is not new — many Apps already do this — from Snapchat and Facebook messenger where you can become a rabbit with a digital mask during a video chat, to “peak finders” which overlay the name and height of mountains on your camera view.</p><p>So if AR already exists, why is ARkit a big deal? ARkit makes it really easy for any developer to add smart AR to iOS apps, and it will be supported on the huge installed base of iOS devices.</p><h3>Why is AR kind of a big deal?</h3><p>The digital world is about to come spilling out of our devices and into the world around us. The world is going to become a mix of things that are physically there, and things that are digitally there. I was going to write “really there”, but corrected it to “physically there”: in many cases the digital world is now more important and real than the physical world.</p><p>You know how more and more devices have been becoming “connected” with bluetooth and wifi? Well, now in one great leap, everything is connected. A door, a tree, or a banana can tell you all about itself. We can stop building screens into everything, because anything can have an virtual screen overlaid via AR. For that matter, eventually we can get rid of TVs and monitors entirely.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F0adc0oCKKKI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D0adc0oCKKKI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F0adc0oCKKKI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0b61179ce6ab0fdd822e0afb3b49feb0/href">https://medium.com/media/0b61179ce6ab0fdd822e0afb3b49feb0/href</a></iframe><p>It’s easy to imagine its usefulness, but it’s impossible to imagine the eventual impact. Of course we’ll find our way to new places easier, probably we’ll find products in stores easier, probably we’ll find our friends and family easier. Will we also make new friends, or partners, easier? I’m sure we can learn how things work faster, and can get useful assistance doing our jobs. Maybe I’ll be able to install an ad-blocker that blocks out the advertisements in the real world - all the billboards and ads on the bus and tram. Or, I will accept a <em>new layer of ads</em> overlaid digitally on the real world in exchange for a cool experience or game.</p><h3>Where are we headed?</h3><p>People are going to be increasingly walking around in their own world. Remember the bands of youth walking around with their phones up in the air chasing the invisible Pokemon last year? Get used to it.</p><p>I think we need to become much more proactive about deciding where we want to go and the future we want to live in. Besides hyping the significance of AR, that’s my reason for writing this article. In a sense we’ve already come quite far with digital augmentation - without calling it that. Most of us carry a smartphone and I’ve honestly been surprised at how much this device has been transforming my relationship with some people. When we meet, they are simply not as <em>present</em> because they are simultaneously in their digital world.</p><p>Back in the 90’s I was so excited by the prospect of VR. Now I understand that simply making something 360 degrees and 3D won’t make a bad thing better. I remember reading how passionate one of the inventors of TV was about it’s power to educate. I wonder what he would think of his invention today.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FYJg02ivYzSs%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYJg02ivYzSs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FYJg02ivYzSs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7b81950dcaec2503cc984d2748bd6b32/href">https://medium.com/media/7b81950dcaec2503cc984d2748bd6b32/href</a></iframe><h3>Magic</h3><p>Despite all the doom &amp; gloom, I can’t help but be excited and hopeful for what the future brings. I’m looking forwards to a lot of surprise, inventiveness, and an amazing outlet for creativity. I’m looking forwards to the world becoming more magical. I love that these folks made a list of things they want to see: <a href="http://www.madewitharkit.com/ideas">http://www.madewitharkit.com/ideas</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FGbpqwUUfMAQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DGbpqwUUfMAQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FGbpqwUUfMAQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3dfc210400de9b121b8e9aceeb7e9019/href">https://medium.com/media/3dfc210400de9b121b8e9aceeb7e9019/href</a></iframe><p>No, this isn’t all going to happen tomorrow. But the ARkit is a watershed moment in that it’s bringing the first big wave of AR experiences to a mass audience. Apple was very clever about making this available on their existing phones. Many of the first apps will be little more than gimmicks, but the interesting thing is that the apps based on this technology will work on other devices <em>when they come out</em>. There is no doubt in my mind that Apple will launch some kind of AR glasses in the near future. These glasses will succeed where others have failed because they will launch out of the box with a collection of proven apps and because after a taste of AR, the people will actually ask for them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39faefd70e9a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-future-content/apples-new-arkit-it-s-a-much-bigger-deal-than-you-think-39faefd70e9a">Apple’s new ARkit, it’s a much bigger deal than you think.</a> was originally published in <a href="https://medium.com/the-future-content">The Future Content</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>