Own productCustom stackGlobal
AstroWay App
Ephemeris maths moved into the browser
The problem
The calculation engine already ran as an API, but a consumer application that calls the server on every redraw pays for that twice: in latency, every time somebody changes a house system or moves the date, and in server cost for every visitor who is only curious. The application had to draw a chart the moment the form is submitted, keep transits and synastry interactive, and carry a public feature surface in six languages without turning into a second codebase.
What the work covered
- Swiss Ephemeris compiled to WebAssembly and executed in the visitor's browser, so a chart is recomputed locally instead of over the network.
- A React application covering the whole chart surface: natal chart, synastry, composite, transits, progressions, solar returns, astrocartography, horary and Human Design.
- Accounts, saved charts and subscription billing on the same database as the rest of the platform, so a customer stays one record instead of three.
- A static public site built with Astro in front of the application, carrying the feature pages, the knowledge base and the blog.
- An embeddable widget, so another site can run the same calculations without an integration project.
Where it stands
The charts are computed on the visitor's machine, the account and the billing stay on ours, and the engine that answers the developer API is the one that draws the app.
Stack
ReactAstroWebAssemblySwiss EphemerisPHPMySQL