Static QR
Best when the charger has a stable identity and the customer flow should be minimal, touchless, and fast.
Apartment and property charging
Public shared chargers
Simpler handoff from sign to phone
Static QR, dynamic sessions, and hybrid rollout logic belong in one operational product. This route explains where each model fits and how the public charging pages map to them.
Best when the charger has a stable identity and the customer flow should be minimal, touchless, and fast.
Apartment and property charging
Public shared chargers
Simpler handoff from sign to phone
Best when the operator needs a session-aware control path with stronger lifecycle visibility and policy checks.
Support-heavy environments
Structured payment checkpoints
Live operator intervention paths
Best when one product must handle mixed site requirements without forcing operators into a migration cliff.
Different site models in one network
Stepwise rollout from static to dynamic
One frontend language across both
These pages let you demonstrate and validate the charging surface before wiring in production backend actions.
/charge
Entry page for public charging actions, demos, and route selection.
/start
Manual or assisted journey for starting a charging session with more context.
/static/[chargerId]
Charger-specific public page for a static QR style experience.
/charging/[sessionId]
Charging-in-progress screen showing status, meter values, and support context.
The right question is not which charging pattern looks more advanced. It is which interaction model creates the least friction while preserving the amount of operator control the site actually needs.