OutSystems Mobile Developer Specialist flashcards
OutSystems Mobile Developer Specialist · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Mobile module
- An OutSystems module type that compiles to native iOS and Android apps, using OutSystems UI Mobile and device-side logic rather than browser rendering.
- Offline mode
- A module setting that enables local SQLite storage on the device so the app can read and write data without a live server connection.
- Sync model
- The per-entity setting (Read Only, Create, Update, Delete, Read/Write) that defines which local changes are pushed to the server during synchronization.
- SyncManager
- The built-in OutSystems component that triggers synchronization and exposes status such as syncing, offline, and error to the app.
- Bottom Bar pattern
- A mobile navigation pattern placing top-level destinations at the bottom of the screen, typical for apps with three to five primary sections.
- OnRender event
- A screen lifecycle event that fires during rendering; heavy logic here causes dropped frames because it runs frequently on the device.
- Local storage variable
- A client-side variable that persists on the device across app sessions, unlike in-memory session variables that reset on restart.
- Safe area
- The region of a mobile screen not obscured by notches, status bars, or home indicators; the UI framework handles insets automatically.
- Provisioning profile
- An Apple-issued file that authorizes an iOS app build to run on devices and be distributed, configured in the OutSystems platform.
- Keystore
- An Android signing file containing the private key used to sign app packages; losing it prevents updating the published app.
- Certificate pinning
- A security technique binding an app to a specific server certificate or public key, reducing man-in-the-middle risk on mobile API calls.
- Remote debugging
- A Service Studio capability that connects to an app running on a device or emulator, streaming logs and allowing breakpoints in client logic.
- Service Studio preview
- A browser-based rendering of mobile screens that does not reproduce native-only features such as camera, GPS, or biometrics.
- Forge plugin
- A reusable component that wraps native platform APIs (camera, GPS, biometrics) and exposes client actions callable from mobile logic.
- Push notification token
- A device-specific identifier issued by APNs or FCM that the app registers with the server to target notifications to that device.
- Deep link
- A URL that opens a specific screen inside a mobile app, requiring handling of unauthenticated entry and parameter validation.
- Client variable
- A device-persisted variable not synchronized with the server, suitable for UI preferences rather than business data.
- Server Action
- Logic that executes on the OutSystems platform and is invoked from client actions; it cannot be called directly from screen expressions.
- Reactive Web module
- A module type that renders in a browser and cannot serve as the screen target of a native Mobile module.
- Aggregate
- A server-side query that retrieves and filters entity data; on mobile it should be combined with caching to reduce round-trips.
- Optimistic UI
- A pattern where the app updates the interface before the server confirms the change, improving perceived performance on high-latency mobile networks.
- Lazy loading list
- A list pattern that renders items incrementally as the user scrolls, avoiding performance degradation from large item counts.
- Session variable
- An in-memory variable scoped to the user session; it is not persisted on the device and resets when the app restarts.
- App shell
- A host application (such as the OutSystems App) that runs generated mobile apps on a device and can deliver over-the-air updates.
- Role check
- A server-side authorization test on exposed REST APIs; client-side checks are advisory and must be duplicated on the server.
- MABS
- The OutSystems mobile build service that compiles module definitions into signed native app packages for distribution.
- Offline entity
- An entity marked as offline-capable so its data is replicated to the device's local database and synchronized with the server.
- Last-write-wins
- The default conflict resolution during synchronization, where the most recent change overwrites earlier ones unless custom logic is added.
- Device permission
- An OS-level grant (camera, location, contacts) declared in the app manifest and requested at runtime before a plugin can use the feature.
- JavaScript element
- A screen element that injects custom JavaScript into the app's WebView context for behavior not covered by built-in actions.
- Screen template
- A prebuilt mobile layout (list, detail, form) from OutSystems UI Mobile that provides consistent navigation and styling.
- App manifest
- The configuration file declaring an app's permissions, icons, and platform settings, generated during the native build process.