Mobile Apps, Embedded Apps...and IoT - session from Data Driven Summit 2014
•Download as PPTX, PDF•
3 likes•2,377 views
By the end of 2014, there will be more mobile phones on the planet than humans. How will we harness these devices to better inform and connect users to their information? And what do we need to consider to truly deliver insights "to everyone, everywhere?" This presentation by Actuate VP of innovation Allen Bonde outlines the latest thinking around mobile and embedded apps and shares what’s possible when it comes to delivering visualizations on non-traditional platforms.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (10)
Similar to Mobile Apps, Embedded Apps...and IoT - session from Data Driven Summit 2014
Similar to Mobile Apps, Embedded Apps...and IoT - session from Data Driven Summit 2014 (20)
Recently uploaded
Recently uploaded (20)
Mobile Apps, Embedded Apps...and IoT - session from Data Driven Summit 2014
- 1. Mobile Apps, Embedded Apps …and the Internet of Things Allen Bonde VP Product Marketing & Innovation Actuate @abonde 1 Data Driven Summit 2014 #datadrivensummit
- 2. Mobile Trends “The number of “microelectromechanical systems” (MEMS) — including sensors and other components in mobile devices like smartphones and tablets — shipped every year has increased more than 6x over the last 5 years.” – Mary Meeker 2 Data Driven Summit 2014 #datadrivensummit Datapoint: Top 5 functional needs for “Mobile BI” according to Dresner Advisory Services: View, Select, Drill down, KPIs, Alerts The creation of custom apps to run on mobile devices used by customers and employees is the “hottest area in software”…and will grow by 50% in 2014, reaching $7B – Forrester
- 3. 3 Data Driven Summit 2014 #datadrivensummit On The Move: Designing for a Mobile- First, Wearable World 3
- 4. Mobile Requirements SMART CONNECTED DEMANDING 4 Data Driven Summit 2014 #datadrivensummit
- 5. 5 Data Driven Summit 2014 #datadrivensummit If ALL apps leverage the same data and tools, we can boost performance and drive reuse Interact + Reuse
- 6. Automate! If data components are centralized, it’s easier to create/send automatic alerts 6 Data Driven Summit 2014 #datadrivensummit
- 7. Design for Today’s Data Consumer Embed To bring data “everywhere” analytic 7 Data Driven Summit 2014 #datadrivensummit apps need to be lightweight, easy to customize, and brand-friendly
- 8. Enterprise Mobile Needs 8 Data Driven Summit 2014 #datadrivensummit Support any platform Tap into data from many sources Secure delivery tailored to profile Display in right format – for device, location Allow users to interact + take action
- 9. 4 Mobile Development Models Entire app developed exclusively in native language specific for each device Native 9 Data Driven Summit 2014 #datadrivensummit Entire app resides on server and is accessible via mobile browser Mobile Web App components reside on server in non-platform- specific language. Native wrapper used for distribution. Hybrid Some app components in native, platform-specific language. Other components on server (non-specific). Native/ hybrid HTML5
- 10. 10 Data Driven Summit 2014 #datadrivensummit IoT Today: Our WEAR Framework and Beyond 10
- 11. The Internet of Everything people things information places 11 Data Driven Summit 2014 #datadrivensummit
- 12. So…what’s the challenge? “The Internet is expanding beyond PCs and mobile devices into enterprise assets such as field equipment, and consumer items such as cars and televisions. The problem is that most enterprises and technology vendors have yet to explore the possibilities of an expanded internet and are not operationally or organizationally ready. Imagine digitizing the most important products, services and assets. The combination of data streams and services created by digitizing everything creates …a lot of stuff to manage ! – Gartner 12 Data Driven Summit 2014 #datadrivensummit
- 13. 13 Data Driven Summit 2014 #datadrivensummit Our Vision: Mobile + Embedded Analytics = Better Engagement 13
- 14. Mobile Development with BIRT Access multiple sources via APIs 14 Data Driven Summit 2014 #datadrivensummit Single sign-on, manage what each user sees/does Combine data Manage access Personalize Role- and task-specific designs Analyze app adoption and behavior in real-time Drive Action Enable interactivity via efficient queries Adapt App Update Server-side updates streamline roll-out
- 15. BIRT in Mobile Environments 15 Data Driven Summit 2014 #datadrivensummit BIRT iHub Scale Store Manage Secure Any platform: Dashboards Alerts Mobile Tablet Desktop Reports Wearable Data objects Analytics Efficient queries sent to server; only relevant data returned to mobile clients Data aggregation Visualization Hub Personalized delivery
- 16. BIRT and IoT – Connecting Your Car to Your Watch Embedded Visualization Data access analytics 16 Data Driven Summit 2014 #datadrivensummit Visualizing IoT data using BIRT, Eclipse.org by Kristopher Clark OBD II Sensor Android App MQTT BIRT iHub Broker F-Type JavaScript Library Alerts Dashboard
- 17. Embed Mobile Web standards Customizable UI JSAPI, REST APIs Automate! 17 Data Driven Summit 2014 #datadrivensummit iHub 3.1 iOS sample iPad apps Low-code tools WEAR framework Android libraries Data access Rich, embedded analytics Interact + Reuse
- 18. Thank You Allen Bonde VP Product Marketing & Innovation Actuate @abonde 18 Data Driven Summit 2014 #datadrivensummit
Editor's Notes
- As we have heard today there are a number of elements needed for creating powerful, portable data-driven apps. This session will drill down on mobility and what’s needed to bring actionable insights to non-traditional devices.
- Of course the backdrop is the explosion of mobile apps and sensors creating new data sources, and also how businesses are looking to deliver business intelligence and insights to new mobile users FitBit, Motion Processor, Car Sensors, NEST thermostats, etc.
- From an Actuate perspective, we can really think of mobile adoption accelerating the notion of “BIRT Everywhere” – and how go about designing for a mobile-first world Paper to Screen to Phone/Tablet to Watch to …? Fridge, car infotainment, thermostat, smart meter, etc.
- If we revisit TODAY’S DATA CONSUMER, it’s clear they are mobile-first, so we need to strive for being relevant (responsive); proactive (portable) and timely (personalized) in our interactions; but from a dev perspective we also need to look to REUSE, AUTOMATE, and EMBED (everywhere) – here’s how… Give me what I need, based on where I’m at AND what I’m doing. Relevancy is key All those combinations, make dev a burden
- Interactivity is key to mobile adoption (just as participation drives social) – recall Dresner study. But if we set out to manage assets like charts, tables, graphs centrally, and SERVE them up as needed, mobile becomes just another delivery method, and ALL our apps leverage the same data and tools – boosting performance (we only send the most pertinent data) and driving reuse – note related to low-code idea With interactivity, less need to develop permutations. Content reuse across devices promotes lower dev cycles
- When data components are centralized, it’s easier to create and send automatic alerts (to Samsung or Apple watch for example) based on location, preference or other events. Alerts are great for connecting to consumers as they interact with brand assets like display ads or retail locations (and in Dresner’s top 5 for embedded BI) …Data also CONNECTS users to your brand via apps and experiences
- Embedding analytics and insights within “non traditional” devices is a huge opportunity…and our approach keeps mobile and wearable apps lightweight, easy to customize and brand-friendly – note related to white label idea Lightweight API for streaming of data to a device… RESTAPI
- Recall, for today’s customer it’s all about the getting the data they want, when they want it, how they want it. SO today’s mobile and wearable platforms need to securely manage, access, analyze, and deliver data from a variety of sources, in a variety of formats and to your customer’s device of choice iHub is the platform that enables all of the above, as a unified, embeddable, API callable, analytics platform. Display: 45 pixels per finger vs 3 pixels for mouse… + screen size = BIG difference
- 4 models…
- Of course you may have noticed the smart watch on the last slide, which is actually an area our team has been exploring under our IoT or Internet of Things initiative…so the next part of this talk actually shares a bit of background for those exploring this area…
- For context, as you may be hearing, enterprises are giving serious thought to the IoT scene. They are finding that an “expanded internet” is something that is being modeled today, with related software and hardware stacks. In fact IoT is just one part of the IoE…
- More broadly here’s what Gartner is saying…That last part I added…but the point is that we have a lot of new sources and a lot of new display options and places to embed analytics! So one challenge is where to FOCUS…fortunately the evolution of BIRT provides some excellent starting points… Fitbit… soon is clothing. What’s next?! Sensors on surf boards, to know when the best “ridable” waves come based on aggregation from the masses.
- BIRT leverages evolving, mobile-friendly web standards like HTML5, plus standard data-connectors like Web Services, JSAPI, REST API…to boost productivity and reach…
- Here’s how we think about supporting key tasks faced by mobile data driven app developers; NOTE we favor native/hybrid approach - Some application components developed in native, platform-specific language (typically Java for Android, Objective-C for iOS). Other application components reside on server, are not platform-specific, and are displayed in a frameless browser (WebView) in the mobile app using HTML5.
- iHub becomes an enterprise mobile app “hub” in this scenario, offering High-Scale, Rich Interactivity, and Low-Code benefits for development teams and their customers
- With iHub at the core, IoT data is just another source, and it can be accessed and visualized within the “information processing” layer, then displayed via a mobile web browser (dashboard), android smartphone (as visualizations) and wearable smartwatch (as alerts) as you saw in our opening show and tell; also as I shared in the opening, the amount of MEMS data is exploding, so we expect this type of use case is going to be a lot more mainstream in the near future
- To wrap up, as discussed our latest iHub with our reference implementations provides a great starting point to explore BIRT, mobile analytic apps, and IoT – the bottom line: this open approach allows us to shift our thinking from developing apps for specific phones, tablets or even smart watches, to envisioning what’s possible when we can reuse key assets and interact with enterprise data on any device (shift discussion to user needs) BIRT iHub is more than just a “reporting” tool. It’s a high performing data engine, married to a visualization platform, which allows for either to be abstracted away, while consistently maintaining user entitlements, business logic, created from the ground up to be embedded.
- For those looking to dig deeper, we have a number of papers, blog posts and videos on Actuate.com related to mobile and IoT, and with this let me open up for questions before we open our cocktail party