large_Crossover Series NFTs.png

medium_Crossover Series NFTs.png

small_Crossover Series NFTs.png

thumbnail_Crossover Series NFTs.png

From Photography to NFT Art: Twisted Digital Landscapes with Nate Hill

From Design System to ‘NFT Design System’: Creating TinyFaces

Neurodiversity and Inclusion: Choosing Kinder Design

medium_652ccf22c8853584bde5553986a4eed0.png

small_652ccf22c8853584bde5553986a4eed0.png

thumbnail_652ccf22c8853584bde5553986a4eed0.png

Web5 is here. Goodbye Web3? TBD.

<p><a href="http://ift.tt/2o2045B">medium bookmark / Raindrop.io</a> |  </p>
<div>
<div>
<div>
<div>
<div>
<p>Front end developer and British implant in San Francisco. Leading the Apps team at Emerge, Cisco’s collaboration innovation labs. htttps://emerge.cisco.com</p>
</div>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<div>
<p><em>Demand for better user experience is increasing at an ever-faster rate and driving expectations of a front end developer’s skillset. The web-to-mobile revolution took a while but mobile-to-VR will happen much faster.</em></p>
<div>
<div><img src="http://ift.tt/2o203i3" alt="1*x8DXerj2QQLZWP80eqtE4w.png"></div>
</div>
<p>Dolly the sheep was cloned in 1997, stuffed in 2003. Since then, many sheep have been cloned in the pursuit of web development.</p>
<p>1997 was a big year. Not because Comet Hale-Bopp appeared. Not because Steve Jobs returned to Apple. Not because Dolly the sheep was born. 1997 was the year I built my first website. Twenty years ago. I’d like to say I was two years old at the time, but that would be a shameful lie.</p>
<p>I found that website recently and, wow, it looks just awful. At the time, it was a modern marvel, obviously. I used Dreamweaver and remember the feeling of pure OCD joy upon discovering that Dreamweaver could output code that was directly editable. Hello HTML. We went on to become good friends. I haven’t kept in touch with Dreamweaver.</p>
<p>Roll forward to 2009. Javascript and CSS joined the party and yours truly had become a Web Developer. There was a lot to contend with back then. Internet Explorer insisted on having its own parallel universe. Doctype plurality was a thing that kept people awake at night, as was the constant, nagging worry that a significant number of users actively disabled Javascript. <strong>It was less about delivering an experience versus catering to the foibles of eccentric browsers, Internet-wary users, and medieval bandwidths.</strong></p>
<p>At the same time, things were easier back then. Essentially, we built for the average desktop computer monitor on the average user’s desk. We thought in terms of resolution. Anyone remember 1024&#215;768? That was a classic. 1366&#215;768, 1280&#215;800 and even 1920&#215;1080 were other increasingly popular resolutions. Then we started to care about media queries and actually altering the experience depending on the screen used. We still thought in terms of resolution, but the web developer’s toolkit had become much more aligned to creating better user experiences. I remember winning business specifically because I took into account different screen sizes and designed for those.</p>
<h3>Things change quicker than expected</h3>
<p>Somewhere amid the flurry of parallax backgrounds, hosted web fonts, and analytics tracking, a new creature reared its head. <strong>Mobile</strong>. I don’t recall exactly when I became aware that mobile was a thing. Somewhere between 2010 and 2012. Probably because one of my <em>desktop websites</em> had been loaded into a mobile browser and looked dreadful. No web developer wants their stuff to look bad (although a quick visit to the Internet will disprove that thought) and so I made sure my media queries accommodated these new smaller screen sizes. Otherwise the <em>mobile version </em>of a website<em> </em>was essentially a hacked-back desktop version and that made for a <strong>bad user experience</strong>. So I found a new unique selling point: I was a web developer who knew how to handle the small number of mobile visitors that your website received. Another weapon in the arsenal of winning web business.</p>
<p>But we were still web developers. If you wanted a bona fide <strong>mobile app</strong> (wait, mobile phones could run apps?) then you were barking up the wrong tree. Why on earth would a business need an actual app? That would require knowledge of the low level languages used across a multitude of different mobile devices. That would require an iOS or Android developer. Rare breeds indeed. A whole new box of frogs. A different kettle of fish.</p>
<p>Then mobile became really popular. How a website behaved on a mobile device became very important. <strong>User experience became a really hot topic</strong>. Users suddenly cared. Web development moved on from the old approach of adaptive design to the shiny new standards of responsive design. We started to care about the intrinsic abilities of the device rather than the number of pixels. 2013 saw the first murmurings of “<strong>mobile first</strong>”, the notion that things should be designed up and not down.</p>
<p>The development of web-driven mobile experiences really started to take off, driven by new frameworks like <a href="http://ift.tt/1aa3DNJ">jQuery Mobile</a>, and later <a href="http://ift.tt/2f1cNRD">Ionic</a> and <a href="http://ift.tt/1ITKHky">React Native</a>. The latter two leverage HTML and native mobile components, meaning we can suddenly build mobile apps. Javascript web app frameworks and libraries such as <a href="https://angularjs.org/">Angular</a> and <a href="http://ift.tt/1jBdybn">React</a> have really helped here, with their ‘think once’ approach to building across different platforms.</p>
<p>I remember interviewing candidates for front end development roles in 2014 and being inconsolably disappointed that many of them still saw mobile as a different skillset. Candidates for similar front end roles in 2015 and 2016 were considerably more interested in mobile and, crucially, would often point to mobile projects in their portfolio. The 2017 front end developer is probably fluent in both ‘traditional’ web and mobile approaches, and is maybe starting to see that the blurred line is fading completely. A fair number have native mobile dev experience too. As I see it, front end roles need to be this way. Just like the Borg, we have adapted. Resistance to progress is futile (again, a quick glance at the Internet may contradict this truism).</p>
<h3>That last new thing has changed already</h3>
<p>So there we go, <strong>mobile is the new web</strong>. But wait. What light through yonder virtual window breaks? I heard the other day that <strong>VR (virtual reality) is the new mobile</strong>. VR could easily be AR (augmented reality). Or MR (mixed reality). Let’s just call it all <strong>XR</strong> (extended reality). VR is the new mobile is the new web. Consider that. If you are a front end developer who can relate to the sequence of events outlined in this post, then you should see all this coming. Here’s my assertion:</p>
<blockquote><p>The 2018 front end developer will be fluent across web, mobile and VR platforms, designing experiences that work compellingly no matter how the user chooses to engage.</p></blockquote>
<p>I’m making this assertion because I see the same pattern of evolution happening once again. <strong>Demand for a better user experience always drives things forward and it matters more in VR than anything previously</strong>. Facebook recently launched <a href="http://ift.tt/2gIROE6">React VR</a>, to sit alongside React Native (mobile) and React (web). Browser-based VR experiences are being championed by the likes of <a href="https://webvr.info/">WebVR</a> and <a href="https://aframe.io/">A-Frame</a>. We are seeing web-driven approaches pop up and coexist with lower level approaches such as <a href="https://unity3d.com/">Unity</a> and <a href="http://ift.tt/1ovyCUD">Unreal</a> (both developed for gaming but with obvious applications to other stuff). This is great for VR. It opens things up for web developers and I believe this will have a very positive effect on user experience.</p>
</div>
</div>
</div>
<div>
<hr>
<div>
<div>
<p>My own team (Apps at <a href="http://ift.tt/2b8ovZ5">Cisco Emerge</a>) is already playing with web-driven VR. The overhead to build is much, much smaller than a low level approach. I took one of our existing video web apps (built with Angular) and jiggled it around to work nicely in 360 wrap-around mode in the <a href="https://www.oculus.com/">Oculus</a> Virtual Desktop. Not perfect — it’s purely HTML, CSS and JS — but a long way from the terrible experience I had initially predicted. It took a few hours and we had a passable prototype to show our customers and testers. The next phase is probably to build in React VR and incrementally improve the experience. I expect that to take days rather than months.</p>
<p>A great US President once said “you cannot escape the responsibility of tomorrow by evading it today”. I doubt he was talking about the evolution of virtual reality, but maybe there was a little bit of front end developer in Lincoln. You never know.</p>
<p><strong>I wonder what the next twenty years will hold?</strong></p>
</div>
</div>
</div>
<div>
<hr>
<div>
<div>
<ol>
<li><em>Dolly the sheep: By Toni Barros from São Paulo, Brasil (Hello, Dolly!) [CC BY-SA 2.0 (</em><a href="http://ift.tt/KcQbXG"><em>http://ift.tt/KcQbXG</em></a><em>)], via Wikimedia Commons</em></li>
</ol>
</div>
</div>
</div>
</div>
<div><a href="http://ift.tt/2o2045B">http://ift.tt/2o2045B</a></div>


Web-driven VR is the next string to a front end developer’s bow

Web-driven VR is the next string to a front end developer’s bow

Top Stories