Doors open to all participants at 9am. Arrive early to snaffle some breakfast and grab a great seat.
An introduction to the unique format of Edge, and how you can participate throughout the day.
There’s little doubt that images are one of the biggest performance bottlenecks and design headaches in responsive web design, but precious little agreement on what to do about it. We have at least three distinct proposals, along with numerous workarounds and polyfill libraries. With real solutions about to become reality, it’s time to make sure we have the best practices right.
‘As slick as native’ is a common boast for HTML5 developers. Web developers are not used to dealing in frame rates and memory consumption, but increasingly they need to. If UX is king, the web can only win when rendering is easier. We need great tools, skilled developers that know how to use them, and improvements in the platform to make the task easier in the first place. This session will address the challenges of rendering interfaces in a performant way in the browser.
Grab a coffee and recharge for the next session.
“Copy this piece of JavaScript” is all too common a refrain among services designed to make developers’ lives easier. Sites that load resources from 30 different hosts are not uncommon. Third party scripts can make it easy to implement good quality solutions for common use cases, but often at the expense of page load performance and security. How should technologies like seamless IFRAMEs, Web components and Content security policy shape the way we deal with third party components?
Websockets have now been with us for several years and enjoy near universal support. WebRTC is just starting out. Chat, live blogging, telemetry/dashboards, remote assist and video conferencing are all proven and popular use cases for real time data. Developers are becoming increasingly comfortable integrating real time elements into new projects, but problems remain with the complexity of scaling a real-time backend, as well as implementing APIs that are practical and useful.
Web applications that work offline are still clearly in demand, but the standards lack support for even fairly basic use cases, and encourage developers to break fundamental navigation models of the web. There are two competing (or perhaps complementary), proposals to improve the situation, but it’ll be a long slog. In the meantime, workarounds remain some of the most hackish in the web world. Are there any workable solutions to 'adding' offline to an existing site? What patterns allow offline to be used today while remaining open to replacement solutions in the future?
“This site is best viewed in...” is a thing of the past, but we’re now largely replacing it with requirements for recent versions of modern browsers, and a fast, always on, unmetered internet connection. Developers may feel that they can’t justify the time required to provide a useable experience for IE6 and its ilk, given the vanishingly small user population, but as the bar will inevitably keep moving higher, let’s work out a best practice for this today.
Bitcoin, Payswarm, Paymill & Stripe, Gocardless, operator billing - there are no shortage of attempts to make payments on the web easier, simpler and cheaper. But payments remain dominated by cumbersome credit card systems and proprietary walled garden systems like App Store billing. Meanwhile, content producers worldwide are struggling to ‘monetise content’. How will we pay for content online in 5 years time, and how should we prepare the technology today to support that?
Enjoy the sunset and direct views of the High Line from The Park, all courtesy of our friends at Facebook. Drinks, networking and making merry all round, hosted by the world's largest social network, in a spectacular setting a short walk from the Google office. Need we say more? See you there.