MDK Project Setup in SAP Build
The concept name provided is "undefined," so no specific SAP developer concept can be accurately defined. Based on the available sources, these tutorials collectively relate to the Mobile Development Kit (MDK), a framework that allows developers to build and deploy mobile applications for both online and offline scenarios on SAP BTP. Developers use MDK to create cross-platform mobile apps with features such as push notifications, deep linking, internationalization, OData-driven CRUD functionality, and NativeScript plugin integration.
Tutorials that teach this
- Tutorial Enable Multi-User Mode for MDK Application
- Tutorial Set Up Initial Configuration for an MDK App
- Tutorial Implement Deep Linking into an MDK Application
- Tutorial Add NativeScript Plugins in an MDK App
- Tutorial Debug Your Mobile Development Kit Application
- Tutorial Enable Push Notifications in the MDK Public Store Client
- Tutorial Handle Error Archive in an MDK App
- Tutorial Implement Deep Linking to Another App from an MDK App
- Tutorial Create Your First MDK Application Using MCP Server
- Tutorial Add Internationalization and Localization to an MDK App
- Tutorial Use OData Annotations to Add CRUD Functionality to an MDK App
- Tutorial Extend Your MDK App With a Map Custom Control (Using Metadata Approach)
- Tutorial Quick Start with the mobile development kit (MDK)
- Tutorial Set Up MCP Server for MDK Development
- Tutorial Add Styling to an MDK App
- Tutorial Consume a REST API in an MDK App
- Tutorial Create a Slider Custom Control in an MDK App (Using Metadata Approach)
- Tutorial Start Your MDK Application in the Editor
Prerequisites
- Concept Mobile app development with SAP Build The concept to be defined is not specified, and the provided sources do not contain sufficient grounded detail to produce a reliable, accurate definition for any clearly identified SAP developer concept. A valid concept name is required to write a documentation entry.
- Concept SAP Mobile Services Account Setup and Configuration No concept was provided, and the supplied sources do not converge on a single, identifiable SAP developer concept that can be defined. A meaningful definition cannot be written without a specified concept to define.
- Concept OData Service Exposure via CAP The concept name provided is "undefined," which does not correspond to a recognizable SAP developer concept that can be grounded in the supplied source snippets. No definition can be responsibly written without a valid concept name and supporting source material.
- Concept SAP Destination Service Configuration The concept name is not defined in the provided sources, so a grounded definition cannot be written. The sources cover related topics such as [inbound communication via principal propagation](https://help.sap.com/docs/btp/sap-business-technology-platform/387b3deb12474762b593d4b1f2b392ad?locale=en-US&state=PRODUCTION&version=Cloud), OAuth 2.0 SAML Bearer Assertion Grant, client certificate authentication, and [routing via destination](https://help.sap.com/docs/btp/sap-business-technology-platform/97d7a02cd6fd4f579fd96f41ee0d0c1d?locale=en-US&state=PRODUCTION&version=Cloud) in the ABAP environment on SAP BTP, but without a defined concept name, no accurate definition can be produced from these snippets alone.
- Concept Model Context Protocol (MCP) Server Integration **Model Context Protocol (MCP)** is an [open standard that defines how AI models and agents can discover, understand, and interact](https://architecture.learning.sap.com/docs/ref-arch/RA0029/10-third-party-mcp-access/readme) with tools, data sources, and services. Developers use it to expose capabilities — such as SAP BTP account administration or the hana-ml Python library — as MCP endpoints that AI agents can consume in a standardized way. For example, the [HANA AI Toolkit local MCP server](https://architecture.learning.sap.com/docs/ref-arch/RA0033/readme) turns the hana-ml library into an MCP-accessible endpoint, enabling third-party agents and AI models to invoke its functionality without custom integrations.
- Concept Business Application Studio (BAS) App Development The provided sources do not contain sufficient information to define this concept. The concept name is listed as "undefined," and none of the source snippets supply grounded, substantive content that could be used to write an accurate 2–4 sentence definition. Please provide a valid concept name and supporting source material.
- Concept SAP Build platform overview The provided sources do not contain sufficient information to define a specific concept, as the concept supplied is "undefined." The sources cover a range of SAP BTP topics — including tools, Classic ABAP development, the Managed Application Router, and Joule Studio — but without a named concept to define, no accurate, source-grounded definition can be produced.
Concepts that build on this
- Concept SAP Mobile Services Log Upload and Configuration
- Concept MDK Extension Control Registration and Consumption
- Concept MDK Multi-User Mode Configuration
- Concept Deep Linking Between Mobile Apps in MDK
- Concept i18n Properties Files for Localization
- Concept MDK SDK Branded Client Build for iOS and Android
- Concept MDK REST Service File and RestService SendRequest Action
- Concept MDK JavaScript Rules and Event Handlers
- Concept Internationalization (i18n) Language Localization
- Concept MDK Actions Configuration (Message/Confirmation Actions)
- Concept Agentic AI Coding
- Concept MDK Error Archive Entity Set Handling
- Concept MDK Section Page Creation
- Concept MDK Push Notification Registration and Configuration
- Concept NativeScript Plugin Integration in MDK
- Concept MDK Custom Extension Controls
- Concept MDK Offline OData Store
- Concept MDK Project Deployment to Mobile Services
- Concept MDK CRUD Operations
- Concept MDK LESS Stylesheet Styling