[Feature]: Support nested properties in Analytics

[JohannesPtaszyk]

What do you want to see in Flocon?

Hey,

Our analytics solution sends event-properties as JSON-structure.
It would be lovely if this is something that could be added to Analytics feature.

So instead of having:

AnalyticsEvent(
    eventName = "opened profile",
    "userId" analyticsProperty "2048",
    "username" analyticsProperty "kevin",
    "age" analyticsProperty "34",
),

Something like:

AnalyticsEvent(
    eventName = "opened profile",
    json = profileEventJson,
),

Would be lovely.
Sadly right now I do not have too much time to contribute, I tried coming up with a solution, but its not that simple to do, as the current structure heavily relies on key-value properties.
Maybe someone else finds time to look into this.

Thank you already

Edit: already created a related discussion a while ago, not sure if it can be closed or we want to use it #459

[florent37]

hey, it can be done, but I Just need to know what would be the type of json in your case, map<String, String> ?

[florent37]

if it's a json object from json.org, it's doable also, but I need to do something like a static function that returns an AnalyticsEvent, because flocon is multiplatform and these classes are only present on android (and maybe desktop)

like :

fun AnalyticsEvent(name: String, json: org.json.JsonObject) : AnalyticsEvent {
    // read the json and create a AnalyticsEvent
}

[florent37]

ah your model got more than 1 level of params ??? I just read the discussion

[JohannesPtaszyk]

Hey, yes, basically, we got some nesting going on, so for example our "application properties" look like this:

"application": {
    "environment": "stage",
    "platform": "app",
    "app": {
        "id": "2025.17.0-debug",
        "version": "2025.17.0",
        "store": "google"
    }
}

And thats next to other properties, which have similar structure.
I know its not the most "standard", but I think e.g. Adobe and Amplitude use these nested structures. Not sure if there are more, but definitely there are some frameworks making use of it :)

[florent37]

in this case, how do you imagine them being displayed on flocon ? because I do have only chips actually

[florent37]

option 1 : an unique chip for this one, but truncate on the listview (it will be displayed fully on the detail view)
option 2 : split this property into multiple params : [application.environment, application.platform, application.app.id, application.app.version, application.app.store]

[JohannesPtaszyk]

I think the chips should just show top-level and then detail view can support looking into the nested things ☺️

Optionally: Clicking a chip could expand it and the expanded have a different color or something. But maybe that's more something to think about later.

Truncation sounds good, maybe even just
"user: [2]" to indicate 2 nester user properties exist 🤔