You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/technical/technology/rap.md
+14-10Lines changed: 14 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,12 @@
1
+
---
2
+
outline: [2, 4]
3
+
---
4
+
1
5
# RAP vs. abap2UI5: Architecture, State & Developer Experience
2
6
3
7
This page provides a structured technical comparison between **RAP (Fiori Elements)** and **abap2UI5**, focusing on architecture, state management, developer workflow, and communication models.
> 🔒 **Both frameworks are cloud-ready and clean-core compliant.** abap2UI5 achieves this **without CDS or OData**, relying solely on released ABAP APIs.
81
85
82
86
83
-
## Conclusion
87
+
###Conclusion
84
88
85
89
-**RAP (Fiori Elements)** is best suited for standardized, metadata-driven applications using CDS, OData, and annotations.
86
90
-**abap2UI5** provides runtime flexibility, backend control, and lower complexity — ideal for dynamic UIs and fast iterations.
0 commit comments