OutSystems Mobile Developer Specialist study plan

Map the full OutSystems mobile delivery lifecycle (module types, screens, client vs server actions, build and publish flow) into a one-page diagram you can redraw from memory

Distinguish Reactive Web App from Mobile App module types and state which exam scenarios require a native mobile module

Configure a local environment with Service Studio and a personal environment, then publish a blank mobile app to a device or emulator to confirm the toolchain works

List the four screens of a typical CRUD mobile app and identify where data fetching belongs (aggregates vs client actions)

Build screens using the mobile-optimized widgets (List, Card, Form, Input) and explain when each is preferred over a generic Container

Implement client variables and session variables correctly and justify each choice against its lifetime and persistence

Wire screen navigation with input parameters and explain how the back stack behaves on mobile devices

Apply the mobile theme and layout patterns so the app renders correctly across phone and tablet breakpoints

Write aggregates with filters, sorting, and joins, and predict the generated SQL shape for each

Decide when to use a server action versus a client action and defend the choice for three given scenarios

Implement local storage for offline-tolerant data and describe its limits compared with server-side persistence

Handle exceptions in client and server actions and surface user-facing error messages without breaking the screen flow

Consume a REST API from a mobile module, map the response to a structure, and handle non-200 responses

Implement authentication and role-based screen access, and explain how the mobile app stores and refreshes the session

Add plugin or native-capability usage (camera or geolocation) and describe the permission prompts on iOS and Android

Profile a screen for unnecessary server round-trips and reduce them

Apply mobile UX rules: touch target sizing, list virtualization, loading states, and empty states

Implement pull-to-refresh and infinite scroll patterns and explain their data-fetching implications

Design for slow and offline networks by defining what the user sees when a call fails

Audit the app against accessibility basics (labels, contrast, focus order) and fix the top issues

Debug mobile-specific failures using the device logs and Service Studio debugger, and classify each failure as client, server, or network

Write and run a test plan covering happy path, validation errors, offline mode, and permission denial

Explain the publish and deploy pipeline for mobile apps, including what triggers a new native build versus an over-the-air update

Identify and fix two common performance anti-patterns (over-fetching in aggregates, heavy client-side loops)

Review the full mobile topic list and rate your confidence per topic on a 1-5 scale

Re-study your three lowest-confidence topics using hands-on mini-builds rather than reading

Practice explaining trade-offs aloud (client vs server action, local storage vs server data, native vs web module) as if answering an interview-style exam question

Rebuild one screen from scratch without reference material to test recall

Take timed practice sets under exam conditions and log every wrong answer with its root cause

Convert each logged mistake into a one-line rule you can recall quickly

Re-run the confidence matrix and confirm every topic is at 4 or above

Do a final pass on the highest-weight mobile topics the day before the exam, with no new material