2. Part of the bigger picture
ā¢ One of the ways to work with SAP
ā¢ IoT landscape
ā¢ Donāt forget UX
3. Mobility and IoT
ā¢ Not only to interact with IoT
ā¢ It also is IoT
ā¢ Wearables
4. Wearables
ā¢ Wearable Opportunities
Real time data, Improved safety, real time collaboration, faster decisions, Hands-Free
Working
ā¢ Risk
Durability, Network reachability, Battery life, User experience, Security
ā¢ VR vs AR.
ā¢ For business processes holding a phone/tablet, isnāt always productive.
ā¢ Hololens
ā¢ Smartwatches
5. Wearables
ā¢ SAP Solutions for Wearables:
ā¢ SAP AR Warehouse picking
ā¢ SAP AR Service Technician
ā¢ Prototypes:
ā¢ Quality Assurance and Onboarding
ā¢ Smart Watch Companion for Technicians (Apple Watch)
ā¢ The Perfect Meeting App (Apple Watch + C4C)
ā¢ Looking into bringing Fiori apps to watches
ā¢ Whats next:
ā¢ More hardware support
ā¢ More prototype apps
6. Web IDE / UI5
ā¢ The tool to build your hybrid apps
ā¢ Test mobile features
ā¢ IoT integration
ā¢ Windows Phone Support
ā¢ Fiori Client support
ā¢ Testing
ā¢ Local Web IDE installation for productive use
ā¢ UI5 Maintenance Strategy
8. SMP 3 / HCPms is ready for you
ā¢ SMP 2.3 still supported
ā¢ Migration starts in the backend
ā¢ Implement Odata
ā¢ And implement it well
ā¢ Deltatokens
ā¢ Skiptokens
ā¢ Conflict management (Etags)
ā¢ Multiple Backends? ļ Integration gateway
ā¢ Downside: No āResultsetcheckersā (Error handling)
9. ā¢ Native apps
ā¢ Better logging and monitoring
ā¢ Easier to learn
ā¢ Hybrid
ā¢ Standards instead of HWC
ā¢ Pitfalls
ā¢ Error handling
ā¢ No delta handling on client
ā¢ Queries through Odata
ā¢ Offline request queue
ā¢ Documentationā¦
ā¢ Broken Batch Request
SMP 3 / HCPms is ready for you
10. SMP 3 / HCPms Documentation
ā¢ SCN
ā¢ Blogs from Daniel van Leeuwen for Kapsel
ā¢ SAP Github with examples
ā¢ help.sap.com now with API docs
11. SMP 3 / HCPms ā the roadmap: SDK
ā¢ Support for Visual studio for developing hybrid / fiori applications
ā¢ Tooling for multiple personas
ā¢ More Kapsel plugins
ā¢ Support for Device sharing across users.
ā¢ Multi factor authentication support
ā¢ Extended wearable support.
12. SMP 3 / HCPms ā the roadmap: Platform
ā¢ SMP:
ā¢ More usage analytics statistics
ā¢ Enhanced 3rd party data support.
ā¢ Offline: Mobile data staging
ā¢ SAP HCPms
ā¢ Fiori Notifications.
ā¢ Leverage HCI. Target Q1
ā¢ More integrated HCP scenarios
ā¢ Cloud Foundry/Openstack
ā¢ In App Messaging: So users can communicate in-app.
ā¢ Release cycle HCPms and SMP.
13. SMP 3 / HCPms ā the roadmap: Agentry
ā¢ Planned to move from proprietary container to cordova
ā¢ Enterprise Cloud
14. Fiori Mobile Services
ā¢ Target Q4 availabilty.
ā¢ All you need to mobilize Fiori in the cloud.
ā¢ Cloud based service on SMP supporting the full mobile lifecycle.
ā¢ Extend Fiori application.
ā¢ Add native features.
ā¢ Build service.
ā¢ Run tests in the cloud, so you can test it as well if you donāt have the devices
themselves.
ā¢ With the possibilities of adding automated test scripts.
ā¢ And integrated with SAP Mobile Place.
ā¢ Usages statistics available. All based on HCPms
16. Fiori Mobile Services ā More Info
ā¢ http://scn.sap.com/community/mobile/blog/2015/11/10/mobilizing-sap-fiori-in-a-
simple-way-new-solutions-announced-at-teched-barcelona
ā¢ http://hcp.sap.com/capabilities/mobile/fiori-mobile.html
ā¢ http://scn.sap.com/community/mobile/blog/2015/11/17/sap-and-microsoft-partner-
by-integrating-sap-fiori-mobile-service-and-microsoft-enterprise-mobility-suite
17. Based on
ā¢ Roadmap Q&A Web IDE and SMP/HCPmS
ā¢ MOB360 : Enhance Mobile Apps with Offline, Push, and Certificate Logon
ā¢ UX208 : SAP Web IDE: Deliver Great Experiences for Browser and Mobile Devices
ā¢ MOB104 : See How Wearable Technology Breeds Successful Internet-of Things-
Solutions
ā¢ MOB201 : Move to the Strategic Mobile Platform Using Best Practices
ā¢ MOB200 : Best Practices to Successfully Develop and Deploy Mobile Applications
ā¢ MOB161 : Enable and Optimize Consumption of Multiple Data Sources for Mobile Apps
Web IDE / UI5 is UX track, but developing hybrid SAP applications needs that too.
SAP AR Service Technician (companion app for SAP WorkManager 6.1+) First costumer is going live now
Lessons learned:
-Ā Ā Ā Ā Error handling:
Ā Ā Ā Ā Mixed sounds about error archive, use a separate object instead
-Ā Ā Ā Ā No delta handling on the client
Ā Ā Ā Ā It is not possible to see which objects changed on the client after sync
-Ā Ā Ā Ā All queries are done via Odata
-Ā Ā Ā Offline request queue
Ā Ā Ā Ā Local Deletes
Ā Ā Ā Ā Multiple updates on the same object
Ā Ā Ā Ā No access to the request queue.
Ā Ā Ā Ā So if you for example create, update and then delete. It will push 3 separate calls to the backend, where none were needed.
-Ā Ā Ā Ā Documentation could be improved. (YES PLEASE!!)
-Ā Ā Ā Ā Broken batch request
Ā Ā Ā Ā To work around that, make a 2nd store, create everything first in that and if you push it to the backend, make a complete batch in the main store and push from there
Tooling for multiple personas: Support for Business expert. Development tool based on Web IDE
More kapsel plugins starting with: Signature Capture, Calendar , Tasks
Enhanced 3rd party data support. First by renewing the tool, but after that more scenarios support and also better scaling
Offline: Mobile data staging. Planned to add as an optional component. Increase performance and decrease load by using deltas
Leverage HCI. So you can also integrate 3rd party systems on HCPms (like you can on premise by using Integration Gateway). Target Q1
Release cycle HCPms and SMP. Starting Q1. HCPms will get monthly releases instead of the quarterly that both now have.
Agentry:
Planned to move from proprietary container to cordova
Enterprise Cloud