Modern Web Apps

Identify values.

Prioritize experiences.

Your internal brand doesn't have to be clever, it just has to exist.

Just like API's, web apps tell a story.

It's a different audience though.


 + Story


I see JavaScript everywhere!

I see JavaScript everywhere!

Careful everyone.....

Modern users demand dynamic Interaction.

"Responsive"  Functionality

What do we focus on?

Content is no longer King

(but still ridiculously important)

Context is King

Context is Continual



Browser Game Changers

  • Chrome
  • Microsoft Edge
  • Firefox*


What about Safari?

JS Engines

V8 (Google)

- Powers Chrome & Node.js (official)


Chakra (Microsoft)

- Powers Microsoft Edge & Node.js (fork)

- Most complete ES2015 Support


SpiderMonkey (Mozilla)

- Original, but aging.

- Powers Firefox



(the new JavaScript)

Why you should care: ES2015

  • This drives the browser.
  • JavaScript is everywhere (fastest growing language), beyond the browser.
  • This is what the new workforce is using.
  • Failure is not an option.

Why you should care: SSL

  • This presents a new limitation to UI dev. 
  • This could slow down development progress.
  • This forces you to be more mindful of security.
  • Even the "experienced" workforce struggles with this.
  • You don't have a choice.



Why you should care: WS

  • Realtime data has never been easier.
  • Requires a different way of thinking (FRP)
  • Changes the gap between UX & Dev.



Why you should care: WebRTC

  • Realtime interactive multimedia is attainable.
  • Requires a different way of thinking (FRP)
  • Blurs the line between UI, Dev, & Network Ops.
  • Potential security vulnerabilities.
  • This is "coming soon"... much faster than you think.

Web Components

  <section class="active">Tab 1</section>
  <section>Tab 2</section>
  <section>Tab 3</section>

Why you should care: WC

  • This will be native in all browsers.
  • This is polyfilled in all major browsers NOW.
  • Will likely introduce new framework vendors.
  • Enforces a strong declarative approach to webdev.

Service Workers

Why you should care: SW

  • Offline & sometimes-connected support.
  • Browser control over the network.
  • New desktop permissions to think about.
  • "Installable" applications = new web paradigm.

Incremental DOM

(not to be confused with virtual DOM)

Functional Reactive Programming

a.k.a. FRP

Progressive Web Apps

Separation of Concerns


Return of Static Sites

  • Brand values and experiences.
  • Tell a story for each app.
  • Responsive++ (Design + Function).
  • Context is King.
  • Change is the only constant.



By Corey Butler


  • 721
Loading comments...

More from Corey Butler