Skip to content

JSON

A JSON property holds structured data, such as the points of a GPS run or a gym session’s heart rate.

JSON is a standard way to write data as named fields and lists. You rarely type it. The phone app, connectors and files fill it for you.

Example: in Workouts, “Route” is a JSON property with the Map format. The entry “Morning run” holds the points the phone recorded, and its entry page draws them as a map.

Formats

A format changes only how the value looks. It never changes what is saved.

Format Holds Shows as Example
Plain (default) any structured data the data, readable a raw payload from a service
Map a list of points, each with a latitude and a longitude a map with the points joined as a line a run, a trip, places you visited
Line a time series: a list of items, each with a time and a number a line over time heart rate during a gym session

One point of a run looks like this (an example; the exact field names are set when it is built):

{ "lat": 54.6872, "lon": 25.2797, "time": "2026-10-27T07:00:05" }

One item of a heart-rate series:

{ "time": "2026-10-27T18:02:10", "bpm": 128 }

A format draws this entry’s own data as a picture. That is not a chart block. A Chart block shows many entries; a format shows one value of one entry.

There is no Location type. A place or a route is a JSON property with the Map format.

Recording

A JSON property can record live from a sensor of your phone.

Record from Saves Example
Off (default) nothing; the property is filled by a connector, a file or you a payload from Google Health
Location a point with latitude, longitude and time Route on a run
Heart rate a heart-rate reading with its time, from a watch, through the phone Heart rate in a gym session
Steps a step count with its time Steps on a dog walk
Altitude a height with its time Altitude on a hike

More sensors come later, in the same way. Each property records from one sensor.

How it works:

  • The property shows Start, Pause, Resume and Stop, like the Stopwatch. A card button can also start it (“Start run”).
  • The phone keeps recording with the screen off.
  • Each point is written to the phone’s disk the moment it arrives, also without a connection. If the app crashes, the phone stops it, or the battery runs out, the points so far are kept. When the app comes back, the recording goes on.
  • The first recording on a phone shows a one-time battery setup screen for that phone’s maker. Some phone makers stop apps in the background to save battery. The screen says which setting to change, with a button that opens it.
  • The points sync like any other change, in batches.
  • The first time you record, the phone asks for permission to use the sensor. Kaizendex uses the sensor only while a recording runs.
  • While it records, formulas that read the property update live.

Where you can record: only in the phone apps. A computer has no GPS. A browser is not offered recording, because it stops when the screen is off. On a computer the property shows its value, and Start says “Recording needs the phone app”.

Automations: while a recording runs, “A value changes” does not start for each point. It starts once, when the recording stops. So “When Route stops recording → notify me” runs once per run. Editing the route later is an ordinary change, and starts it again. See Triggers.

Add a file

Drop a GPX or GeoJSON file on a JSON property with the Map format. Its points fill the property. GPX and GeoJSON are common file formats for routes; most sports apps export them. This works on every device.

Settings

Setting What it does Example
Name The name you see. Route
Format Plain, Map or Line. Map
Record from Off, location, heart rate, steps or altitude. Location
Hide the start and end when shared (Map only) Shared and public copies leave out the points near the start and the end. On by default, 200 m. You still see the full route. On, 200 m

Why hide the start and end: most runs start and end at home. With this setting on, a run you share or publish does not show where you live.

How it shows

Place Shows
Card a small map for Map, a small line for Line
Entry page the full map or line; the readable data for Plain
While recording the entry fills the phone’s screen: the map grows and the formulas update
List and table row not decided yet

In the folder

How a JSON value is written in the entry’s file is not decided yet. Raw data from a service (a payload) is also kept in its own store, so the app can read it again later.

AI, formulas and privacy

  • AI reads the data, under the collection’s AI setting.
  • Formulas read the list: distance(prop("Route")) gives 5.2 (km), average(prop("Heart rate"), "bpm") gives 128. See Formula.
  • Privacy: a recording follows the Where and AI choices of its collection and entry, like any value. See Your privacy choices.