Reusable Components
Use approved prebuilt modules to reduce duplicated development where their source, security, compatibility, ownership, and lifecycle are understood.
Legacy mobile development context
Building Engaging Mobile Apps with SAP Mobile Platform (SMP)
SAP Mobile Platform is a legacy enterprise mobile application platform used for B2B, business-to-employee, and B2C application scenarios across on-premise and cloud-connected landscapes.
SMP 3.0 was designed to simplify mobile app development and is now historical technology rather than a recommendation for a new implementation. Existing applications should be evaluated for business use, device and operating-system support, back-end dependencies, identity, security, data protection, offline behavior, maintainability, licensing, vendor support, and modernization options.
SMP development model
Key Features of SMP
SMP historically provided resources for creating mobile applications connected to SAP and other enterprise systems, with on-premise or cloud deployment patterns and cross-platform development goals.
Cross-platform development aims to build an application once and deploy it across different mobile operating systems. Actual portability depends on the technology, native capabilities, device APIs, client versions, operating-system changes, accessibility, testing, distribution, and ongoing support.
Historical SMP 3.0 additions
What’s New in SMP 3.0?
These features describe the SMP 3.0 era. Availability, security, compatibility, partner libraries, and continued support must be verified before relying on any component.
Drag-and-Drop HTML5 Apps
Use visual tooling for appropriate user-interface design while preserving code review, accessibility, testing, responsive behavior, performance, and maintainability.
REST APIs
Connect applications and data through governed REST services with explicit authorization, contracts, validation, versioning, errors, observability, and support ownership.
Customizable Apps
Assess every historical application or library against current provenance, rights, compatibility, security, business fit, upgrade path, and support.
Legacy architecture
Technical Breakdown of SMP 3.0
Four primary components make up the SMP 3.0 architecture. Treat each component as a legacy dependency to inventory, validate, secure, and support or replace.
1. Sybase Unwired Platform (SUP)
Historical infrastructure for developing and deploying enterprise mobile applications and connecting them to different data sources. Record active servers, clients, synchronization, interfaces, credentials, environments, and support dependencies.
2. Sybase Mobiliser
For any active Sybase Mobiliser deployment, establish its real functions, integrations, security requirements, dependencies, support position, and replacement path directly from the current landscape.
3. Syclo Agentry
Historical tooling for designing, deploying, and managing a mobile application lifecycle with complex workflows across back-end systems such as SQL, XML, and Java-based services. Confirm current clients, workflows, interfaces, and supportability.
4. SAP Integration Gateway
Legacy runtime and administration context for connecting applications with data sources and defining or managing services. Validate the Gateway Management Cockpit, service repository, OData contracts, monitoring, access, and target integration architecture.
Potential enterprise value
Benefits of SAP Mobile Platform (SMP)
Seven historical platform goals provide a useful modernization checklist. Test their current relevance against the active application, device estate, architecture, support position, and modernization cost.
1. Seamless Integration
Connect approved back-end data sources through governed interfaces. Integration quality depends on contracts, security, monitoring, reconciliation, error handling, and ownership.
2. Comprehensive Platform
Inventory the development, deployment, management, integration, security, testing, and support tools actually present instead of assuming the legacy ecosystem remains complete.
3. Multi-Device Accessibility
Support relevant mobile and desktop experiences only where device compatibility, responsive design, identity, accessibility, security, connectivity, and user support have been validated.
4. Enterprise-Grade Development Environment
Assess reliability, security, scalability, separation of environments, release control, observability, recovery, and maintenance against present enterprise requirements.
5. Innovative Mobile Apps
Prioritize mobile applications that solve a verified business need and can be operated responsibly. Business value, growth, and efficiency remain outcomes to measure.
6. Rapid Deployment
Use reusable patterns and controlled delivery where appropriate, but measure deployment speed across device types, testing, distribution, security review, support preparation, and release evidence.
7. Cost and Time Efficiency
Compare stabilization, continued operation, remediation, rebuild, replacement, and retirement using actual license, infrastructure, implementation, testing, support, risk, and transition costs.
Legacy application decisions
How Can SCMNEXX Help You?
Building, operating, or replacing SAP-connected mobile applications requires significant investment, trust, and accountable technical work grounded in verified scope and competencies.
Expert Team
Confirm the functional, mobile, integration, security, testing, infrastructure, data, user-experience, and change skills required for the verified application scope before assigning delivery responsibilities.
Continued Support
Agree post-deployment monitoring, incident, device, operating-system, interface, security, release, documentation, vendor, and escalation coverage rather than implying unlimited ongoing assistance.
Review mobile platform risk