|
| 1 | +## Technology Overview |
| 2 | + |
| 3 | +### abap2UI5: Over-the-Wire for SAP (2023+) |
| 4 | +abap2UI5 applies the Over-the-Wire principle to SAP UI5 apps. The backend (ABAP) defines UI5 XML Views and ViewModels, which are sent to the browser. A generic, static UI5 app dynamically renders this content. |
| 5 | + |
| 6 | +- **Frontend stays generic & static** |
| 7 | +- **No custom JavaScript development needed** |
| 8 | +- Perfect for CRUD-heavy business applications |
| 9 | +- Inspired by modern Over-the-Wire frameworks like Hotwire, Livewire |
| 10 | +- Addresses SAP's "Clean Core" approach by keeping custom code backend-driven |
| 11 | + |
| 12 | +### RAP / Fiori Elements: Backend-driven SPA (2019+) |
| 13 | +The **RESTful Application Programming Model (RAP)** standardizes how SAP applications expose data and services via OData V4. **Fiori Elements** apps use these services to render UIs client-side in the browser. |
| 14 | + |
| 15 | +- Developers define CDS Annotations in ABAP |
| 16 | +- UI is built dynamically by the UI5 Fiori Elements runtime (SPA) |
| 17 | +- Suitable for standard apps with CRUD patterns |
| 18 | +- Reduces custom UI development, but still SPA complexity (OData Metadata handling, UI5 runtime) |
| 19 | + |
| 20 | +### UI5 Freestyle: Custom SPA (2010+) |
| 21 | +UI5 Freestyle apps offer full control over the frontend. Developers build custom UI5 applications using JavaScript, XML Views, and UI5 Controls. |
| 22 | + |
| 23 | +- Allows highly customized, interactive UIs |
| 24 | +- Full SPA architecture in the browser |
| 25 | +- Requires frontend expertise (JavaScript, UI5 skills) |
| 26 | +- More flexible, but also more complex in development & maintenance |
| 27 | + |
| 28 | +### Web Dynpro ABAP: Server-Side Rendering (2003+) |
| 29 | +Web Dynpro ABAP is SAP's traditional web UI framework. It renders HTML on the server and sends complete pages to the browser for each interaction. |
| 30 | + |
| 31 | +- Component-based UI framework fully implemented in ABAP |
| 32 | +- Classic Server-Side Rendering paradigm (SSR) |
| 33 | +- Suitable for transactional SAP applications |
| 34 | +- Limited flexibility for modern UI patterns, but robust and widely used |
| 35 | + |
| 36 | +### ITS Mobile: Legacy SSR for Mobile Devices (2000+) |
| 37 | +**Internet Transaction Server (ITS) Mobile** converts classical SAP Dynpro (SAP GUI) screens into HTML pages for mobile browsers. |
| 38 | + |
| 39 | +- Simplifies legacy app mobilization (e.g., warehouse scanners) |
| 40 | +- Pure server-side HTML rendering (SSR) |
| 41 | +- Very basic UI, optimized for keyboard-based navigation |
| 42 | +- Still relevant for niche use cases with rugged devices |
| 43 | + |
0 commit comments