IBM Connect 2013 BP210 Using a Mobile Approach

BP210 Using a Mobile Approach:
Strategies for Mobilizing your Domino
Applications
Graham Acres | President, Brytek Systems Inc.

© 2013 IBM Corporation © 2013 Brytek Systems Inc.

Graham Acres

 IBM Lotus Notes® Developer/Designer since 1992 (v2.1)
 Experienced as both an IBM customer and Business Partner
 Currently focus on application development (XPages, Mobile)
 Brytek is an IBM Business Partner based in Vancouver
 Featured on NotesIn9; Speaker at Lotusphere, MWLUG, CCLUG
 Blog: www.bleedyellow.com/blogs/brytekblog
 Twitter: @gacres99
 LinkedIn: www.linkedin.com/in/grahamacres

 Away from work
– Coach minor hockey
– Cyclist, Ride to Conquer Cancer © 2013 Brytek Systems Inc.
2

Agenda

 Learn Something About Ourselves

 The Mobile Universe

 Mobile Device Management

 You Are Already A Mobile App Developer!

 Mobile Project Challenges & Strategies

 How to Get Started

 Resources

 Q&A

3 © 2013 IBM Corporation © 2013 Brytek Systems Inc.

The Following Trademarks Are Used in This Presentation

 IBM Lotus Notes®
 Domino®
 Lotusphere®
 BlackBerry®
 iPhone®
 iPad®
 iPod®
 Android™
 Gmail™

4 © 2013 Brytek Systems Inc.

I Wear a Lot of Hats
 Project Manager
 Business Analyst
 Developer
 Administrator
 Infrastructure
 QA Analyst
 Help Desk


Agenda







 Resources

 Q&A


Learn Something About Ourselves

 How many smart / mobile devices do you own/use?
– For Work or Personal
– Smart phones
• BlackBerry®
• AndroidTM
• iPhone®
– Tablets
– eBook Readers
– Anything that can connect to Facebook
• WiFi Enabled
• iPod®

 How many do your kids own?


“ It's an important way to think
about it: there is no such thing as
mobility or mobile working, there
is just work. Aspects of work are
done in different places and as
people now need access to IT for
every part of their work, that has

”
to be extended.

Source: Rob Bamforth, Principal Analyst Communication Collaboration and Convergence, Quocirca © 2013 Brytek Systems Inc.

Agenda







 Resources

 Q&A


Where does your significant ROI kick in?

Location-based & advanced
mobile input solutions

Business Intelligence &
Business Value

access to knowledge
systems

Alerts & Notifications
with workflow
automation

Mobile Web Pages

Email & Calendar

Solution Complexity


Agenda







 Resources

 Q&A


Why MDM?

 BYOD!
 Coalfire BYOD survey. Key findings include:
– 84 percent of individuals stated they use the same smartphone for personal and
work usage.
– 47 percent reported they have no passcode on their mobile phone.
– 36 percent reuse the same password.
– 51 percent of respondents stated their companies do not have the ability to
remotely wipe data from mobile devices if they are locked or lost.
– Despite the growing awareness, 60 percent of respondents are still writing down
passwords on a piece of paper. There is progress, however, as 24 percent reported
using a password management system, 11 percent are saving an encrypted document
on their desktop and 7 percent have a document saved on their desktop.
– Nearly half of all respondents - 49 percent - stated their IT departments have not
discussed mobile/cybersecurity with them.

 http://www.virtual-strategy.com/2012/08/14/byod-survey-47-percent-users-lack-password-smartphones-accessing-company-files


Why MDM?

 More than ½ of all users don’t lock their devices
 Almost 1 in 5 devices are lost each year
 Mobile devices are predicted to be the new malware frontier
 There is a policy disconnect between IT and end users
 Can you protect your mobile fleet against cost overruns, loss/theft, abuse &
international roaming etc.

 Device Security: Goldilocks solution (Carnegie Mellon / Microsoft Research)
– http://www.csoonline.com/article/712639/byod-means-users-want-a-goldilocks-answer-for-device-security

 Employee Mobile Device Agreement from Absolute Software
– http://www.absolute.com/shared/whitepapers/abt-byod.pdf

 Paul Mooney review of the MDM market
– http://www.pmooney.net/2012/12/the-mobile-device-management-market

Agenda







 Resources

 Q&A


Traditional Notes/Domino Application Goes Mobile

* Based on a real situation
 Consider a traditional Notes workflow application
– Approval processing
– No browser interface

 Consider this application before we started carrying mobile phones
– Approval notices received in Notes mail
– Link back to the Request document

 Consider this application after we started carrying mobile phones
– Approval notices received on your mobile device
– Domino converts that link into a URL
– The mobile phone launches the link in its browser

 What is the user experience / expectation?
 And Yes, this example makes you a mobile application developer
– Put it on your resume!

Agenda







 Resources

 Q&A


Challenge #1: Who Is Driving The Bus?

 As with most things, the Business is driving the need to provide mobile
applications
– Did anyone get a tablet for Christmas?

 Therefore the Business expects IT to have the answers
– Who owns the device?
– Standardize on a device and/or a platform – or not?
– A litany of other questions

 IT must be prepared to address the needs of the Business, while balancing:
– Limited budgets
– Limited resources
– Aggressive timelines
– A rapidly changing landscape in the mobile space


Strategy #1

 Decide what device(s) to support

 Drives the following:
– Application development approach
– Security approach
– Support approach

 Device fragmentation can make
application delivery and support
very challenging.
– Limited options
– Increased cost


Challenge #2: Mobile Application Development Platform

 What approach do we use to build the app?
– XPages / Web / HTML5 ?
– Native ?
– Use a Tool ?

 Can we take advantage of existing application logic without rewriting?
 Can our existing development staff build the app or do we need to hire someone?
 How do we handle security?
 Are there graphics or web UI standards we need to follow?
 Does the app need to support multiple languages?


1 Web
Application 2 Hybrid Web
Application
(web with a wrapper)
3 Native
Application 4 Native
Application
using MEAP
Advantages Advantages Advantages Advantages

• Familiar architecture • Familiar architecture with a • Most flexibility • Development time less than
native app wrapper custom native app with non-
• Server side deployment • Full access to device APIs to specializes resources
• JavaScript Frameworks create virtually any application
• JavaScript frameworks available including Dojo, • Multi-platform
available including Dojo, jQuery Mobile, Sencha • Improved speed (translates to
jQuery Mobile, Sencha a “snappier” UI) • Server-side deployment with or
• Some offline capabilities without additional
• Responsive design Challenges infrastructure
• Integration to device APIs
• Multi-platform (includes feature • Higher learning curve for • Many use common
phones) • Multi-platform developers – mobile context programming languages such
and mobile tools (emulators, as XML, JavaScript, CSS,
Challenges Challenges plug-ins for IDE, etc.) HTML

• User experience may be less • Newer devices only • Specialized skill set that can • Many have tight integration
effective; response times be difficult to find depending with services on the device
• User experience may be less on your geography
• Lack of device integration effective • Platform, OS & device
• Single platform changes should NOT impact
• May need different JavaScript • Push notification requires your application
libraries to support different additional infrastructure • Platform, OS & device
devices changes will impact your Challenges
• Requires understanding of application
• Need active connection HTML5 (still an evolving • Integration with platform API's
standard) • Requires application is dependent on the MEAP you
• XPages (Dojo) does not deployment to devices use
support older browsers • Extensions to access device
(BlackBerry) APIs may not be cross-device • Some have limited offline
compatible capabilities
• Requires application • Requires application
deployment to devices deployment to devices


Strategy #2: Mobile Application Development Platform

 That’s great, but how do I choose?

web vs native mobile apps search

 Prepare to read for the next couple of hours, or days, and remain without a clear
answer
 Bottom line: there is no wrong choice
– As with all things, it depends on your needs

 Gartner: Despite market consolidation, the MADP market continues to evolve
rapidly. In addition, the evolving nature of mobile applications and infrastructure
makes it difficult for an enterprise to select a strategic MADP vendor. Concentrate
on finding a development platform that will satisfy most, if not all, of your short
term needs and be prepared to re-examine your choice every few years.

Gartner Report: Magic Quadrant for Mobile Application Development Platforms, April 26, 2012, G00230529


 Let’s argue that a Web app is the way you want to go:

 1. XPages Extension Library Mobile Controls
– Not ready for prime time, but a good place to get some knowledge

 2. jQuery Mobile, et. al.
– Lots of options, but the mobile world is moving fast

 3. Responsive design
– Mobile devices are just one more way to consume content / apps
– Bootstrap
– http://responsive.is



 Let’s argue that a Native app is the way you want to go

 You get the best experience
 Each has its own development language
– $$$$

 Organizations have found that a web app ultimately didn’t fit their needs once it
was built
– Facebook web app >> Facebook native app
– Zuckerberg: “relying on HTML5 was one of Facebook’s biggest mistakes to date”


Factor Web Usually Native Usually
Superior Superior
Quality of experience
Application sophistication, native APIs
Addressable audience
Cost per user
Agility
Technical risk
Tool vendor risk
Operational flexibility (e.g. poor signal)
Flexible / custom security strategies
Supportability
Competitive issues and user expectations
Availability of developer skills


Enterprises are
migrating away from
tactical mobile
application silos
(supporting a single
application) to
strategic platforms
that can support
multiple applications,
manage devices, and
secure data and
transport.



 Gartner Magic Quadrant (2012)
– Adobe – Kony
– Andanza Technologies – Microsoft
– Antenna – Netbiscuits
– Appcelerator – Research In Motion
– Apple – salesforce.com
– Data Systems International (DSI) – SAP
– Dojo – Sencha
– FileMaker – Spring Wireless
– Google – Syclo
– IBM – Usablenet
– jQuery Mobile – Verivo Software

27 Gartner Magic Quadrant for Mobile Application Development Platforms, Published: 26 April 2012 © 2013 Brytek Systems Inc.

Challenge #3: Infrastructure Support

 If this is your first mobile app, who in IT has the knowledge to support it?
 Do you need to support a Mobile Enterprise Server (BES or other)?
 How will you manage the traffic the application will generate?
– Will there be impact to the servers and the network?
– Will existing data plans support the traffic the application will generate?

 How many different mobile device models and operating systems do you support,
not to mention how many different vendors?
 What are your security policies and risk tolerance levels?
 What if the mobile device vendor makes a new operating system and several new
device models available right in the middle of your project?
– How likely is it that you can control how quickly the people on the project upgrade
devices?


Strategy #3: The Infrastructure You May Need

1. IT experience
– IT staff will need to add to existing support skills and must be involved in projects early
and often

2. Mobile Enterprise Servers
– MDM and MAM solutions will require training, and policies
• BYOD: You MUST have an MDM solution
– If you have a BES, and not a lot of experience with it, you have the option of excluding it
from your mobile application environment, but, this will drive your choice for application
development platform



3. Application (Domino) Servers / Network Configuration
– Be prepared for needing additional domains for mobile specific traffic to your servers.
• For Native and MEAP
– Development, Test, Production
– Naming standards
• m.acme.com
• www.acme.com/mobile

4. Network Traffic
– Biggest factor is the application, so the requirements and resulting architecture will tell
you how much data you can expect.
– Generally, vendors are very aware of bandwidth considerations and will take advantage
of caching.
– With the advent of ATMs, banking transactions exploded from 41M in 1978 to 11.2B in
1998



5. Security
– Take advantage of Domino
– Keep in mind how much data is on the device. Generally your e-mail policy is going to
cover applications, so if you don't have a mobile e-mail policy it's time.
– Use MDM tool to secure the corporate data on the device
http://mashable.com/2012/10/10/mobile-security-infographic/

6. Mobile Device Vendor Release Schedule
– Stay aware of the release schedule from device vendors and manage your project
timeline, and users, accordingly.
• Christmas


Challenge #4: What Functionality Will the Application Have?

 Managing the expectations of the Business team in terms of requirements
– Are they engaged in the first place?
• Is there a clear business case?
– It should just work shouldn't it?
• 700,000 apps in both the Apple and Google app stores
– Think mobile?


Strategy #4: Engage and Educate Your Business Team

 Does the business team understand the functional and user interface
considerations of a smart phone or tablet vs. a browser or Notes client when
providing requirements?
 Usability in the mobile context should be of primary concern
– You must design a compelling mobile app user experience

 Here is a question you can ask …


“Why?”

30 seconds
3 minutes
30 minutes

Strategy #4: Engage and Educate Your Business Team

 There are many other application design constraints that are not necessarily
obvious
– Network latency (user expectations!)
– Network availability
– The pipe is only so big … and so are your data plans
– Constantly evaluate what and how you are sending data to the device
– Screen sizes, input mechanism, processor speed, memory
– Battery life!
– Security


Challenge #5: Testing in the Mobile World

 How are you going to test the application?
– Can you simulate traffic for the number of users the app is expected to support?

 Who to involve?
– Geographic coverage
– Language considerations
– Do you have a champion?

 Do you have a test server?


Strategy #5: Mobile Application Testing

 Test early. Test often. Test in context.
– Pilot group
– Differing devices (BYOD)
– Differing security
– Differing geography
• Network coverage
– Tools for load testing
– Positive attitude
– Help Desk


Strategy #6: Deploying a Native App

 Consumer vs. Enterprise context
– Enterprise Server / MDM / MAM
– Web-based (OTA – over the air)
– Tethered to a workstation
– AppStore, BlackBerry® AppWorld, Google Play, 100+ others


Strategy #7: Supporting a Mobile Application

 Will the Help Desk support the application?
– Have they been involved from the start of the project?
– How do users report problems on their mobile device?

 Make the devices being supported available to the Help Desk

 Train users to take a screen shot and mail it to the Help Desk


Return on Investment

 How will you evaluate success?
– How will you know if anyone is using the application?

 Catalog.nsf shows application usage
– Not a lot of detail, but useful for mobile-specific applications

 Domlog.nsf shows unique IP address access to applications
– A little custom view development gives even more information


Agenda







 Resources

 Q&A


How to Get Started

 Learn to think like a mobile app developer, not a classic web (or Notes) developer
 Build a simple app to get experience working in a mobile world
 Web is easiest because it’s what we already know
 Pick a simple app
– Employee Phone List
• Click to call HTML: <a href="tel:+16049167526">Brytek Systems Inc.</a>
– Agenda
– Office Locations

 Use XPages controls in ExtLib, or not
– Good support for iOS and Android
– BlackBerry, not so much

 Mobilizer


How to Get Started

 Move on to applications with a high business value
 Workflow applications
– Approvals
– Focus on the minimal amount of information required to approve or deny a request
– Time reporting

 Investigate Responsive Design
– Bootstrap (Twitter)
– Collaboration Today

 Investigate MEAPS
– Within the Domino world
– Outside the Domino world


Agenda







 Resources

 Q&A


Resources

 Chris Pepin
– IBMer with focus on Mobile, Twitter: @ChrisPepin

 John Jardin
– ICS BP, mobile dev guru, Twitter: @john_ukuvuma

 Breaking Development – Mobile Web Design
– Twitter: @bdconf

 Laurie Desautels
– PWC, digital, UX, web & mobile strategy, Twitter: @ldesautels

 John Wargo
– The View, Twitter: @johnwargo

 Podcasts – Taking Notes Podcast 2012 Mobile Series
 LUGs (MWLUG, AusLUG, BLUG, UKLUG, IamLUG)


Other Sessions at Connect

 SHOW112 : Building Your First Mobile Application Using XPages
– Tue, 29/Jan 04:30 PM - 06:15 PM, Swan Osprey 1 & 2 (NOW!)

 SPOT104 : How We Built CollaborationToday.info in a Matter of Weeks
– Wed, Jan 30, 1:30 - 2:30 PM, Swan SW 1 - 2

 ID505 : BYOD at IBM: IBM Lotus Notes Traveler, IBM Connections Mobile, IBM
Endpoint Manager and More! (Chris Pepin)
– Thu, 31/Jan 08:30 AM - 09:30 AM, Dolphin S. Hem I

 AD404 : NSF2IPA: Delivering Your Existing IBM Domino Application as a Mobile
App.
– Thu, 31/Jan 10:00 AM - 11:00 AM, Dolphin S. Hem II

 Previous Sessions - Get the Slides
– JMP103 : Get the “ Jump” on Mobilizing Your IBM Notes and Domino Applications
Today!
– SPOT103 : Delivering the Offline Mobile Experience with Teamstudio Unplugged


Agenda







 Resources

 Q&A


Q&A and Thank You!

 Fill out your evaluations

 Graham Acres
graham.acres@brytek.ca
(604) 916-7526
Twitter: @gacres99
www.brytek.ca


Legal disclaimer
© IBM Corporation 2013. All Rights Reserved.
The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in
this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are
subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials.
Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the
terms and conditions of the applicable license agreement governing the use of IBM software.
References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or
capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a
commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any
activities undertaken by you will result in any specific sales, revenue growth or other results.
All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and
performance characteristics may vary by customer.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
All references to Acme refer to a fictitious company and are used for illustration purposes only.


IBM Connect 2013 BP210 Using a Mobile Approach

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (19)

Destaque

Destaque (8)

Semelhante a IBM Connect 2013 BP210 Using a Mobile Approach

Semelhante a IBM Connect 2013 BP210 Using a Mobile Approach (20)

Último

Último (20)

IBM Connect 2013 BP210 Using a Mobile Approach

Notas do Editor