2013/04/28 13:30 Gabi Zedik (IBM Research), “Mobile First: Future Directions in Mobile Development and Runtimes”

IBM Impact Conference, Las Vegas, Nevada

This digest was created in real-time during the meeting, based on the speaker’s presentation(s) and comments from the audience. The content should not be viewed as an official transcript of the meeting, but only as an interpretation by a single individual. Lapses, grammatical errors, and typing mistakes may not have been corrected. Questions about content should be directed to the originator. The digest has been made available for purposes of scholarship, posted by David Ing.

Following the GTO session by Steve Abrams, in the first track that IBM Research has run at the Impact conference


Mobile First isn’t just a name, it’s a way of thinking of mobile

Mobile has GPS, personalized

Unlike other technologies where think about processes first, have to put the person in the centre

New consumption patterns

  • Omnichannel:  physical, mobile,social, video and web
  • Context fusion: apps used to perform an single task, based on context (roe, mobile)
  • App-centric
  • Activity burst
  • Apps chained

Re-imaging businesses

  • Radical simplification: core objective, enable in one or two interactions, e.g. Instagram, Bump
  • Extreme personalization
  • Participative behavior
  • World-as-an-interface
  • Zero barrier to entry

Mobile First has disruptive impact on IT delivery infrastructure

  • “Systems of engagement”:  read about these on web
    • Engagement capabilities
    • Scalable delivery infrastructure
  • “Systems of record” are legacy systems

Challenge:  data used to live on the system of record, life was easy, would access from a fat client or browser

  • For mobile devices to work effectively, some of the data needs to move off systems of records, to be cached on the device in continuous client experience
  • Then need to synchronize data, make sure it’s secure

Mobile First Delivery Middleware is different from Traditional Web App Server

  • Functional requirements
  • Programming model attributes
  • Run-time deployment and management attributes: heteorgeneity in middleware stacks, number of programming languages

Emphasis on mobile developers, different from those in cloud

  • Need a higher level of abstraction, a layer above a cloud
  • Focus on building mobile application:  usability is important
  • Would like to configure a dashboard on server side, and access that
  • Care less about virtual machines, who started the service, they just want them there
  • Would like to avoid writing code on the server side (although sometimes do need to write)

Mobile Enteprise Application Platform Solution (MEAP) 2011-2012

  • Familiar Worklight diagram

Other companies more focused on mobile developers

  • Convergence: mobile enterprise platforms are converging with mobile infrastructure services

IBM Mobile Runtime Platform (with Systems of Engagement)

  • Mobile Industry  Platform and App Services
  • Mobile Backend as a Service (MBaaS) — non-SQL, more JSON or SOAP, need a transformation
  • Foundational Services — different security models
  • Cloud runtimes and frameworks (PaaS Fabric)
  • Software Defined Environment

Research Runtime and Industry Services

Session 1169:  Space-Time Aware Services for the IBM Platform

  • Location is becoming central for what we do
  • Linking operational decision management becomes important
  • Link with uncertainty, work in a proactive event-driven way (so that if have situations, handle, or change)
  • Combine with visual analytics, to define investigative services

Spatial extension to Websphere eXtreme Scale

  • Important on how to represent data, structure in an efficient way so don’t have to go across all of the servers

Secure Mobile First Enterprise Data Services

  • Unlike a laptop that could be owned by an enterprise, mobile devices are much more exposed
  • Bringing device into enterprise, have to manage private and enterprise data, e.g. e-mail that requires authentication, and can’t be copied to the private side of the device

Omnichannel:

  • Have many mobile devices
  • Vision, would like seamless way of moving across devices and across people
  • e.g. start on desktop, them move to device on car (without sending it by e-mail) to start in the same point
  • Ability to synchronize across applications, across operating systems, across users, in a seamless experience
  • Challenge:  want to share across devices, operating systems, applications
  • For an application doing it across devices

Scalable enterprise mobile messaging service

  • A lot happens in RESTful APIs
  • Sometimes using messaging, delivering system to system with certain throughputs
  • Sometimes pub-sub mechanisms
  • MessagingSight to handle so many devices at throughput required

Want agility from development point of view

  • Looking at how to simply:  Rapdi App Development of Data-Centric Mobile Enterprise Apps, session 1211

Research Development Lifecycle Tools as a Service

  • Testing
  • Application security and certificatoin
  • NitroGen:  Rapid LOB app constructoin
  • Usability and accessibility
  • DevOPS:  delivered in an Enterprise App store

Mobile challenges and accessibility support are more important in devices, e.g. could have light outside, can’t hear in a noisy environment

Research projects:

  • Smarter mobile commerce:  customer context –> omnichannel interaction –> authentication and payment
  • Context inference engine
  • Presence zones, enabling in-store personalized services
  • ARISTO:  Actionable, personally tailored knowledge ad the decision point, e.g. augmented reality application that could sort, compare prices, filter out (as opposed to calling your wife)
  • Smarter mobility:  e.g. transportation, logistics

In Brazil lab:

  • Smart Board
  • Citizen Sensor: reporting on city problems when they encounter them
  • City Companion: helping tourists, the blind