Nuclos App architecture: generic interpreter of the REST API, endpoints (/rest, /rest/bos, boMetas, query, boGenerations), Flutter, dio, riverpod.

Language: Deutsch · English

Architecture and API

How the app works: generic REST interpreter, endpoints used, technology stack and roadmap.

Auf dieser Seite

At its core the app is an interpreter of the generic Nuclos REST API. It contains no Nuclet-specific code; structure, layout and data come from the server at runtime.

Endpoints used

POST /rest                         Login (Cookie-Session, JSESSIONID)
POST /rest  (anonymous/anonymous)  Anonymer Login
GET  /rest/bos                     Entitäten (Business Objects)
GET  /rest/boMetas/{id}            Metadaten (Attribute, Typen, titlePattern)
GET  /rest/bos/{id}?offset=&chunkSize=   Datensätze (mit Paging)
POST /rest/bos/{id}/query          Suche/Filter
     boGenerations                 Neuanlage (Objektgeneratoren)

Technology

Flutter (native rendering engine), Material 3.
dio + cookie manager (cookie_jar) – REST with a cookie session (like the Web Client's withCredentials).
flutter_riverpod – state management.
local_auth + flutter_secure_storage – biometrics & secure credential storage.
fl_chart (charts), file_picker/image_picker (attachments/camera).

For the Web build, CORS is required on the server because of the cookie session. Not needed on iOS/Android.

Roadmap

Extended detail/edit forms (all attribute types, reference picker, subforms).
Native features: barcode scan, push, further biometrics.
Advanced search/filter via query.

Related pages

What is the Nuclos App?

Concept.

Öffnen →

Editing records

Generic layout.

Öffnen →