: Big milestones for the Gemini family of models!
In the first part of this blog series, we explored how SAP Joule was introduced into the SAP SuccessFactors Mobile app and what it means for users. In this follow-up, we dive deeper into the architecture, execution approach, and the outlook for the mobile experience.
SAP BTP is a platform engineered to integrate, automate, extend, and build AI-powered business applications and processes across the enterprise. SAP Build is the unified application development and process automation solution on SAP BTP, enabling personalization and efficiency at scale.
SAP Mobile Services is the channel for mobile development in SAP Build. Developers can use the Mobile Development Kit or SAP BTP SDK for iOS or SAP BTP SDK for Android to create robust, native apps. Administrators can manage the full app lifecycle – from configuring push notifications and securing data to enabling offline access and monitoring usage. SAP apps such as SAP Mobile Start, SAP Ariba, and SAP Service and Asset Manager are all built on this foundational technology stack.
The SAP BTP SDK for iOS and SAP BTP SDK for Android provide a reusable component enabling SAP apps to deliver a consistent and native Joule experience across mobile platforms. SAP Mobile Start also integrated this component to bring Joule to its users last year.
SAP SuccessFactors Mobile has long leveraged the Fiori frameworks from the BTP SDKs to provide a consumer-grade experience in an enterprise context. These frameworks follow Fiori design guidelines while maintaining a fully native feel on iOS and Android. Given this deep integration with the BTP SDKs, adopting the Joule component was a natural progression.
As outlined in the first blog, SAP SuccessFactors Mobile supports multiple onboarding mechanisms – QR code, deep link, company search, secret code, and MDM-based provisioning. While this flexibility has been key to serving a diverse user base, it also meant that delivering a seamless, SSO-based Joule experience required a significant architectural shift.
To meet this challenge, SuccessFactors leveraged SAP Mobile Services and the SAP BTP SDKs for iOS and Android. This allowed for secure authentication and efficient routing of Joule-related traffic while maintaining compatibility with existing onboarding flows. The change was foundational – requiring careful planning to avoid disruption for millions of active users worldwide. SAP SuccessFactors Mobile app now connects to both the SuccessFactors (for standard HR data/functions via APIs) and to the Joule service for AI queries.
A key decision in the SAP Mobile Services adoption journey was determining how SAP SuccessFactors Mobile Server would communicate with SAP Mobile Services. A lightweight multi-tenancy model was adopted, allowing SAP Mobile Services to operate behind the scenes while preserving the familiar admin experience within SuccessFactors. New APIs were introduced to maintain this continuity while supporting increased scale.
The adoption of SAP Mobile Services had significant implications for SuccessFactors’ client logic and the SAP BTP SDKs for iOS and Android. For instance, the SuccessFactors app transitioned to using the SecureStore Module provided by the BTP SDKs, which securely manages and stores sensitive PII user information on mobile devices. By leveraging this module, SuccessFactors eliminated the need to maintain its own database and reduced reliance on third-party libraries. Another example is that SuccessFactors required administrators to configure preferred browsers via MDM and enforce digits-only passcodes. To accommodate these requirements, the SAP BTP SDKs introduced new capabilities in its Foundation and FioriFlows frameworks.
This collaboration offered mutual benefits, as features developed in response to SuccessFactors’ needs were implemented in a reusable way, including enhanced MDM support and new authentication capabilities. As a result, these features became part of the Mobile Services platform offering, benefiting not only other SAP apps but also external customers and partners building their own mobile solutions with SAP Build. The effort also enabled SuccessFactors to audit and simplify its own mobile app, streamlining processes in some cases by retiring underused functionality or tightening security – for instance, limiting the ability to delete other profiles to the primary user.
A massive undertaking of this scope required a phased approach from SuccessFactors, even for features already supported. Future releases will enable SuccessFactors to enable Joule on shared devices.
The foundation laid so far has set the stage for long-term collaboration. For example, SuccessFactors’ mobile apps will soon feature an updated home page built using BTP Fiori SDK UI components. We’re also planning to enable users to capture photos of documents in response to HR flows in Joule for use cases where attaching certificates or receipts is required. Once synergies are fully realized, SuccessFactors will be well-positioned to leverage more SAP Mobile Services capabilities such as offline functionality. Another exciting area of joint exploration is on-device AI models. As mobile devices become increasingly powerful, both teams are keen to investigate how AI workloads can be intelligently distributed between the cloud and the device – unlocking even more responsive and personalized user experiences.
Please note that all future items mentioned here are indicative and may change subject to SAP’s strategic interests.
Beyond the features themselves, this collaborative effort continues to drive SAP’s broader strategic vision of being AI-first and Suite-first. With Joule now live in SAP SuccessFactors Mobile, and with a strong outlook ahead, the foundation is set for a smarter, more unified SAP experience – on every device, for every user.
Note: This article has been co-authored by @VinodDevarajan @ptawade @Xeric @SamZhang @SamiLechner @_dk
In the first part of this blog series, we explored how SAP Joule was introduced into the SAP SuccessFactors Mobile app and what it means for users. In this follow-up, we dive deeper into the architecture, execution approach, and the outlook for the mobile experience. SAP BTP is a platform engineered to integrate, automate, extend, and build AI-powered business applications and processes across the enterprise. SAP Build is the unified application development and process automation solution on SAP BTP, enabling personalization and efficiency at scale.SAP Mobile Services is the channel for mobile development in SAP Build. Developers can use the Mobile Development Kit or SAP BTP SDK for iOS or SAP BTP SDK for Android to create robust, native apps. Administrators can manage the full app lifecycle – from configuring push notifications and securing data to enabling offline access and monitoring usage. SAP apps such as SAP Mobile Start, SAP Ariba, and SAP Service and Asset Manager are all built on this foundational technology stack. The SAP BTP SDK for iOS and SAP BTP SDK for Android provide a reusable component enabling SAP apps to deliver a consistent and native Joule experience across mobile platforms. SAP Mobile Start also integrated this component to bring Joule to its users last year.SAP SuccessFactors Mobile has long leveraged the Fiori frameworks from the BTP SDKs to provide a consumer-grade experience in an enterprise context. These frameworks follow Fiori design guidelines while maintaining a fully native feel on iOS and Android. Given this deep integration with the BTP SDKs, adopting the Joule component was a natural progression.As outlined in the first blog, SAP SuccessFactors Mobile supports multiple onboarding mechanisms – QR code, deep link, company search, secret code, and MDM-based provisioning. While this flexibility has been key to serving a diverse user base, it also meant that delivering a seamless, SSO-based Joule experience required a significant architectural shift.To meet this challenge, SuccessFactors leveraged SAP Mobile Services and the SAP BTP SDKs for iOS and Android. This allowed for secure authentication and efficient routing of Joule-related traffic while maintaining compatibility with existing onboarding flows. The change was foundational – requiring careful planning to avoid disruption for millions of active users worldwide. SAP SuccessFactors Mobile app now connects to both the SuccessFactors (for standard HR data/functions via APIs) and to the Joule service for AI queries.A key decision in the SAP Mobile Services adoption journey was determining how SAP SuccessFactors Mobile Server would communicate with SAP Mobile Services. A lightweight multi-tenancy model was adopted, allowing SAP Mobile Services to operate behind the scenes while preserving the familiar admin experience within SuccessFactors. New APIs were introduced to maintain this continuity while supporting increased scale.The adoption of SAP Mobile Services had significant implications for SuccessFactors’ client logic and the SAP BTP SDKs for iOS and Android. For instance, the SuccessFactors app transitioned to using the SecureStore Module provided by the BTP SDKs, which securely manages and stores sensitive PII user information on mobile devices. By leveraging this module, SuccessFactors eliminated the need to maintain its own database and reduced reliance on third-party libraries. Another example is that SuccessFactors required administrators to configure preferred browsers via MDM and enforce digits-only passcodes. To accommodate these requirements, the SAP BTP SDKs introduced new capabilities in its Foundation and FioriFlows frameworks.This collaboration offered mutual benefits, as features developed in response to SuccessFactors’ needs were implemented in a reusable way, including enhanced MDM support and new authentication capabilities. As a result, these features became part of the Mobile Services platform offering, benefiting not only other SAP apps but also external customers and partners building their own mobile solutions with SAP Build. The effort also enabled SuccessFactors to audit and simplify its own mobile app, streamlining processes in some cases by retiring underused functionality or tightening security – for instance, limiting the ability to delete other profiles to the primary user.A massive undertaking of this scope required a phased approach from SuccessFactors, even for features already supported. Future releases will enable SuccessFactors to enable Joule on shared devices.The foundation laid so far has set the stage for long-term collaboration. For example, SuccessFactors’ mobile apps will soon feature an updated home page built using BTP Fiori SDK UI components. We’re also planning to enable users to capture photos of documents in response to HR flows in Joule for use cases where attaching certificates or receipts is required. Once synergies are fully realized, SuccessFactors will be well-positioned to leverage more SAP Mobile Services capabilities such as offline functionality. Another exciting area of joint exploration is on-device AI models. As mobile devices become increasingly powerful, both teams are keen to investigate how AI workloads can be intelligently distributed between the cloud and the device – unlocking even more responsive and personalized user experiences.Please note that all future items mentioned here are indicative and may change subject to SAP’s strategic interests.Beyond the features themselves, this collaborative effort continues to drive SAP’s broader strategic vision of being AI-first and Suite-first. With Joule now live in SAP SuccessFactors Mobile, and with a strong outlook ahead, the foundation is set for a smarter, more unified SAP experience – on every device, for every user. Note: This article has been co-authored by @VinodDevarajan @ptawade @Xeric @SamZhang @SamiLechner @_dk Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
Bruni and Williams fly through Q1 into the finals! 