# Applications

Version 0.1, 2026-10-12. Source: https://developer.nrgon.net/applications

The top layer that nrgon maintains. What a person opens: a portal, an app on a tablet,
a PDF. Every application shows results from the intelligence layer and data from the
data layer. None holds data of its own.

```cards
dashboard | Operator portal | Sites, batteries, state of charge, today's plan, savings, outages. Light and dark theme. For the people who run the fleet.
plan | Controller | The day plan per site: charge and discharge windows, grid limits, what the battery does now and why. Monitoring first; control where the equipment and the agreement allow.
phone | Configurator | A sizing conversation in big type: site type, consumption, rhythm, outage needs, solar, generator, grid. Ends in a PDF proposal. iPad, Android and web from one definition file.
tablet | Showroom | The demos as one app for sales visits: homes, stores, factories, utility, the platform itself. iPad and Android, works offline.
apps | Simulator | A site with a battery over a day, played forward, for explaining what the platform does with a tariff and a load.
report | Reports | Proposal, weekly report, final report. One A4 page where one is enough. PDF and Markdown.
```

## Mobile

iPad and Android apps are native shells around the same content as the web pages, so a
change is made once. Screens, questions and numbers come from one definition file; the
harness proves iPad, Android and web agree before a release.

## Solutions on top

A solution is an application built for one customer or partner. It uses the layers below
and may add its own front end. Examples of the shape:

```cards
solution | EMS for an equipment maker | The maker's units, the nrgon data and intelligence layers, a portal in the maker's name.
solution | Fleet swap app | A driver app and a fleet portal on top of station data and the plan models.
solution | Second-life assessment | Pack health and capacity reports from battery management data, for a reseller.
solution | A customer's own dashboard | The customer's team reads the same data through their own front end.
```

Each sits on the data layer at least. The more of a solution runs on the nrgon cloud, the
less has to be rebuilt for the next one.