OutSystems Associate Developer study guide
OutSystems Associate Developer · Work through your exam, one topic at a time.
The Associate Developer (ODC) is an OutSystems certification exam that, in OutSystems' own description, "focuses on the fundamentals of OutSystems web and mobile app development." It is aimed at developers who are new to OutSystems Developer Cloud (ODC) and who build simple web and mobile apps, and OutSystems positions it as one of the first steps in becoming a certified OutSystems developer. The exam runs 120 minutes and is offered in English, Español, 日本語, and Português (BR); the fee is $200 US. The OutSystems Associate Developer study guide has 4 sections and about 1,191 words.
01Fundamentals of OutSystems Web App Development
An OutSystems web app is a module (Reactive Web App for modern screens) containing a set of elements: Entities (data model), Screens (UI pages), Server Actions (server-side logic), Client Actions (browser-side logic), Roles (authorization), and UI Flows (navigation containers). Reactive Web Apps render in the browser and use client-side data fetching, so screens are composed of Blocks (reusable UI components) and Widgets (Table, Form, List, If, Button).
335 words, about 2 min02Fundamentals of OutSystems Mobile App Development
A Mobile App module in OutSystems targets native mobile devices using a Reactive-like architecture. The key differences from web: screens are optimized for touch, offline capability matters, and the app is packaged and distributed through app stores.
292 words, about 1 min03ODC Development Basics for New Developers
OutSystems Developer Cloud (ODC) is the cloud-native evolution of the platform. It uses a containerized, Kubernetes-based architecture, separates build and runtime environments, and introduces concepts like Stages (Development, Test, Production) and Assets (reusable modules published to a catalog).
272 words, about 1 min04Building Simple Web and Mobile Apps
The build workflow is consistent across web and mobile: model data → build screens → wire logic → secure → test → deploy . Start by defining Entities and their relationships (one-to-many, many-to-many).
292 words, about 1 min