A standards based alternative to
         'the app way'
             J.Boye 11, Aarhus, 9th November



                             Kristian Norling
                                     Findwise
                                  KristianNorling
Region Västra Götaland
     Public sector
  50.000 employees
© Region Västra Götaland
Abstract
Working hard on mobile intranets/web as well. We have
choosen to not going the app way, rather building on
html5 first then "compiling" the web site for app
market distribution. A killer combo. After a decade of
developing for the desktop, the new frontier for the
Region Västra Götaland (VGR) intranets is mobile.
Kristian will present how VGR has solved a few of the
problems associated with mobile development. A
practical hands-on presentation on how one
organization is developing apps for their mobile
intranet.
Agenda
• Developing mobile intranet apps, our
  thinking on the subject
• Developing for many platforms at once, is it
  even possible?
• How to develop intranet apps
• Things we think will happen in the (near)
  future
• Do's and don’ts
“8. In both internetworked markets and
among intranetworked employees, people
are speaking to each other in a powerful
new way.”
                  The Cluetrain Manifesto
We think mobile...
• Simple to use
• Simple in design
• Simple technical architecture
Developing mobile intranet apps
   • The default standard browser we use is...
     ancient
   • We have to support standards only
   • NO plug-in technology
   • We have standardized on Android and iOS
     for mobile
   • WebKit is IT
Developing for many
platforms at once
 • New, dual strategy for intranets:
    Mobile targeted first - Desktop second...
 • Forget about developing native apps as a
    priority - not cost effective in the long
    run...
 • Open Source - lots of good stuff
 • Stick to the HTML5 standard (and others
    by W3C
 • do not EVER consider Flash etc.
How do we develop
intranet apps?
 • We eat our own dog food
 • Developing accordingly to our reference
   architecture (SWE)
 • We do clean HTML5 front end apps - on
   top of...
 • Nice robust REST / WS based backend
 • Use (something like) PhoneGap to make
   “native” apps for distribution.
Check out the prototype
http://vgr-portalramverk.dev.netrelations.se/mobile/home.html
Things we think will happen
in the (near) future
 • Notifications
 • GPS
 • Kamera
 • Bluetooth
 • The Phone is the Security Device
 • Thoughts on a mobile phone enhanced
   intranet (SYS 64738 blog post)
Do's
• DO consider a dual strategy - or even
  better focus on...
• DO mobile primarily
• DO use HTML5
• DO use PhoneGap or other similar options
... and don’ts
• Do NOT develop for the lowest common
  denominator - skip IE7 and IE8
• Do NOT use plug-in technology
• Do NOT develop native apps
• Do NOT listen to me... make up your own
  mind
Questions?
Thank you!
kristian.norling@findwise.com
findwise.com
sys64738.se
twitter.com/kristiannorling
www.slideshare.net/kristiannorling
www.linkedin.com/in/kristiannorling

A standards based alternative to 'the app way'

  • 1.
    A standards basedalternative to 'the app way' J.Boye 11, Aarhus, 9th November Kristian Norling Findwise KristianNorling
  • 2.
    Region Västra Götaland Public sector 50.000 employees
  • 4.
  • 5.
    Abstract Working hard onmobile intranets/web as well. We have choosen to not going the app way, rather building on html5 first then "compiling" the web site for app market distribution. A killer combo. After a decade of developing for the desktop, the new frontier for the Region Västra Götaland (VGR) intranets is mobile. Kristian will present how VGR has solved a few of the problems associated with mobile development. A practical hands-on presentation on how one organization is developing apps for their mobile intranet.
  • 6.
    Agenda • Developing mobileintranet apps, our thinking on the subject • Developing for many platforms at once, is it even possible? • How to develop intranet apps • Things we think will happen in the (near) future • Do's and don’ts
  • 7.
    “8. In bothinternetworked markets and among intranetworked employees, people are speaking to each other in a powerful new way.” The Cluetrain Manifesto
  • 8.
    We think mobile... •Simple to use • Simple in design • Simple technical architecture
  • 9.
    Developing mobile intranetapps • The default standard browser we use is... ancient • We have to support standards only • NO plug-in technology • We have standardized on Android and iOS for mobile • WebKit is IT
  • 10.
    Developing for many platformsat once • New, dual strategy for intranets: Mobile targeted first - Desktop second... • Forget about developing native apps as a priority - not cost effective in the long run... • Open Source - lots of good stuff • Stick to the HTML5 standard (and others by W3C • do not EVER consider Flash etc.
  • 11.
    How do wedevelop intranet apps? • We eat our own dog food • Developing accordingly to our reference architecture (SWE) • We do clean HTML5 front end apps - on top of... • Nice robust REST / WS based backend • Use (something like) PhoneGap to make “native” apps for distribution.
  • 16.
    Check out theprototype http://vgr-portalramverk.dev.netrelations.se/mobile/home.html
  • 17.
    Things we thinkwill happen in the (near) future • Notifications • GPS • Kamera • Bluetooth • The Phone is the Security Device • Thoughts on a mobile phone enhanced intranet (SYS 64738 blog post)
  • 18.
    Do's • DO considera dual strategy - or even better focus on... • DO mobile primarily • DO use HTML5 • DO use PhoneGap or other similar options
  • 19.
    ... and don’ts •Do NOT develop for the lowest common denominator - skip IE7 and IE8 • Do NOT use plug-in technology • Do NOT develop native apps • Do NOT listen to me... make up your own mind
  • 20.
  • 21.