Service AppsC++ / eUIMIT · v0.1.0Important — Extended Stack

eServiceApps — Embedded Service Applications

eSocial · eRide · eTravel · eWallet · eHealth Mobile

A suite of consumer-facing service applications for EoS devices. eSocial, eRide, eTravel, eWallet, and eHealth365 Mobile — all running natively on EoS hardware with offline-first architecture, end-to-end encryption, and EIPC integration with the EoS platform.

View on GitHub →Read the Docs

Service Apps

Offline-First

Architecture

E2E

Encryption

BLE + WiFi

Connectivity

How It Works

Step-by-step flow — from initialization to output.

Install Service Apps

Service apps are installed via eApps. They require network connectivity (WiFi or cellular) for their cloud backends, but all core functionality works offline with eDB local storage.

# Install service apps
eapps install esocial eride etravel ewallet ehealth365-mobile

Authenticate with eVault

Service apps use eVault for secure credential storage. OAuth tokens, API keys, and user credentials are stored encrypted in eDB with keys derived from the eBoot chain of trust.

// Store OAuth token in eVault
evault_store("esocial.oauth_token", token, strlen(token));

// Retrieve it later
char token[256];
evault_get("esocial.oauth_token", token, sizeof(token));

Use Offline-First Architecture

All service apps write to eDB first, then sync to the cloud when connectivity is available. This ensures the app works even without network access.

// eRide: store trip locally, sync when online
void record_trip(trip_t *trip) {
    // Always write to eDB first
    edb_doc_t doc = trip_to_doc(trip);
    edb_collection_insert(db, "eride_trips", doc);

    // Sync to cloud if online
    if (eos_net_is_connected()) {
        sync_to_cloud("eride_trips");
    }
    // Background sync task handles offline trips
}

Usage Examples

Real-world scenarios showing eServiceApps in action.

eHealth365 Mobile Integration

The eHealth365 Mobile app receives real-time biometric data from a HEALTH-BAND Neuro wristband via BLE and displays it on an EoS tablet.

// eHealth365 Mobile: BLE → eNI → eAI → display
#include <eos/ble.h>
#include <eai/model.h>

void health_monitor_task(void *arg) {
    ble_device_t band = ble_connect("HEALTH-BAND-Neuro-4821");
    eai_model_t hrv = eai_model_load("hrv_analysis.eai", EAI_BACKEND_CPU);

    for (;;) {
        health_frame_t frame;
        ble_recv(band, &frame, sizeof(frame));

        // AI analysis
        float hrv_score = eai_infer_scalar(hrv, frame.rr_intervals);

        // Store in eDB
        edb_doc_t doc = health_frame_to_doc(&frame, hrv_score);
        edb_collection_insert(db, "health_log", doc);

        // Update UI
        ui_update_biometrics(&frame, hrv_score);
    }
}

Features

The shape of eServiceApps at a glance.

eSocial

Social networking client with end-to-end encrypted messaging, offline post drafting, and eDB sync.

eRide

Ride-sharing and navigation app with offline maps, route optimization, and trip logging in eDB.

eTravel

Travel planning app with offline itineraries, boarding pass storage, and currency conversion.

eWallet

Digital wallet with NFC payments, transaction history in eDB, and eVault-encrypted credentials.

eHealth365 Mobile

Companion app for eHealth365 devices. Real-time biometric dashboard, AI health insights, and HIPAA-compliant eDB storage.

Offline-First

All apps write to eDB first and sync to cloud when connectivity is available.

E2E Encryption

All user data is encrypted with AES-256 keys stored in eVault.

BLE + WiFi

Connect to eHealth365 devices via BLE; sync to cloud via WiFi or cellular.

Role in the EoS Ecosystem

Why eServiceApps matters — and what breaks without it.

eServiceApps brings consumer-grade service applications to EoS devices. They demonstrate that EoS is not just for industrial and medical applications — it is a complete consumer platform. eServiceApps also serves as the reference implementation for how EoS apps should handle cloud connectivity: offline-first with eDB, secure credential storage with eVault, and EIPC integration with the EoS platform.

Depends On

EoS Kernel — all service apps run as EoS processes

eDB — offline-first local storage for all service data

eVault (eOffice) — secure credential and token storage

EIPC — inter-app communication and platform service access

eAI — AI features (health analysis, route optimization, fraud detection)

Enables / Powers

Consumer EoS devices — tablets, smart displays, wearables

eHealth365 devices — biometric data visualization and analysis

Smart city infrastructure — eRide and eTravel for urban mobility

Open source on GitHub

MIT licensed and developed in the open. Issues, discussions, and pull requests welcome.

⌥ embeddedos-org/eApps

Embedded Service Applications

C++ / eUIMITv0.1.0

Open ↗

In the EoS stack

eServiceApps is highlighted in the layer below.

App layer

UI / browser layer

Data layer

AI runtime

Neural interface

IPC fabric

EoS kernel + HAL

eos-platform profile

eBootloader

Build / IDE / Sim

Pairs well with

Sibling components that eServiceApps commonly works alongside.

eDB

Offline-first local storage for all service app data.

eOffice Suite

eVault (part of eOffice) provides secure credential storage for service apps.

eAI

AI features: health analysis, route optimization, fraud detection.

Technical Specifications

Apps	eSocial, eRide, eTravel, eWallet, eHealth365 Mobile
Architecture	Offline-first with eDB local storage and background cloud sync
Encryption	AES-256 for data at rest (eVault); TLS 1.3 for data in transit
Connectivity	BLE 5.0, WiFi 802.11ac, LTE (via modem HAL)
Health Standards	HIPAA-compliant data handling for eHealth365 Mobile
License	MIT