This document discusses different types of apps that can be created with OutSystems, including traditional web, reactive web, and mobile apps. It explains that reactive web and mobile apps offer a state-of-the-art architecture, the ability to create apps that delight users with a great experience, and a unified developer experience. The document also provides a comparison of traditional web, reactive web, and mobile apps in terms of code reusability, target devices, user experience, performance, access to device capabilities, offline capabilities, deployment and updates, and distribution.

1. Introducing
OutSystems Apps
Types of Apps
Programming Model
What App Should I Choose?
Service Studio Workflow

2. Types of Apps
2

3. Traditional Web
Types of Apps
3

4. Traditional Web Mobile
(Phone and Tablet)
Reactive Web
Types of Apps
4

5. Mobile
(Phone and Tablet)
Reactive Web
Types of Apps
Traditional Web
5

6. Reactive Web and Mobile Apps
State-of-the-Art Architecture
Follow the most recent standards and best practices, protecting you while making you
move fast in an always changing landscape.
6

7. Reactive Web and Mobile Apps
Apps that Delight Your Users
Deliver apps that move at the speed of thought. Increase customer engagement:
check! Making your employees more productive: check! Make everyone fall in love
with your apps: check!
State-of-the-Art Architecture
Follow the most recent standards and best practices, protecting you while making you
move fast in an always changing landscape.
7

8. Reactive Web and Mobile Apps
Unified Developer Experience
Use low-code to create any app, for any device. Enjoy a great unified developer
experience so you can deliver fast and change faster.
State-of-the-Art Architecture
Follow the most recent standards and best practices, protecting you while making you
move fast in an always changing landscape.
Apps that Delight Your Users
Deliver apps that move at the speed of thought. Increase customer engagement:
check! Making your employees more productive: check! Make everyone fall in love
with your apps: check!
8

9. Programming Model
9

10. Programming Model
10

11. Programming Model
11

12. Reactive Web Mobile
(Phone and Tablet)
Which App Should to Choose?
12

13. Common logic for all devices and
screen sizes.
Reactive Web
Common logic for supported native
mobile platforms, and supported
browsers for PWAs.
Mobile
(Phone and Tablet)
Code Reusability
13

14. A browser.
No installation is needed.
Reactive Web
Native mobile apps run in Android
and iOS. PWAs run in any device with
a supported browser.
Mobile
(Phone and Tablet)
Target Device and Audience
End-User Requirements
14

15. Responsive layout for all screen sizes
and types.
Reactive Web
Dedicated mobile UI patterns and
experiences.
Mobile
(Phone and Tablet)
User Experience
15

16. Performance designed for the client
side, with smart mechanisms to
optimize the data transfer.
Reactive Web
Performance designed for the client
side, with smart mechanisms to
optimize the data transfer.
Mobile
(Phone and Tablet)
Performance
16

17. HTML5 supported device capabilities.
Reactive Web
Native mobile apps and PWAs access
a range of device capabilities.
Mobile
(Phone and Tablet)
Access to Device Hardware
17

18. No offline capabilities.*
Reactive Web
For storing offline data, native mobile
apps use local storage and PWAs use
browser storage.
Mobile
(Phone and Tablet)
Offline Capabilities
(*) Currently not available.
18

19. Updates are automatic when users
refresh the browser page.
Reactive Web
Native mobile apps can update
automatically. PWAs update
automatically when the app detects a
new version.
Mobile
(Phone and Tablet)
Deployment and Updates
19

20. Share the link of the app with users.
Reactive Web
In-house distribution or through app
stores. Users can run a PWA directly
from your website, and add the app
icon to the device home screen.
Mobile
(Phone and Tablet)
Distribution
20

21. Service Studio Workflow
21

22. Service Studio Workflow
22

23. Service Studio Workflow
23