Desk Notes
Recorded critiques of real payload dumps, plus the taxonomy worksheets. Useful before a firmware freeze; not a substitute for live review.
Bangkok studio · device telemetry
The fleet already speaks. Most product teams never learn the dialect.
Cloudfeaturebase teaches IoT App Analytics as a craft: how companion apps, firmware events, and cloud traces should be instrumented so a hardware team can argue from signal instead of anecdote.
Invoices after a scoping call. This site does not take cards or invent scarcity.
2,140
annotated device-hours in the studio archive, reviewed with working product teams.
“We arrived with twelve MQTT topics and a Grafana wall nobody trusted. After the firmware-cohort worksheets, the Q3 review finally used one definition of ‘online’.”
Flagship programme
Device Signal Studio
An eight-week cohort for product, firmware, and analytics people who share one connected app. You leave with a telemetry contract, a funnel that survives OTA, and a dashboard pair — one for ops, one for product — that do not contradict each other.
Next Bangkok evening cohort invoices at THB 34,200. Recordings exist; live critique is the point.
How the studio teaches
We treat events as promises, not decorations.
01
Contract before chart
Every property on a device event is named, typed, and versioned before anyone opens a visualisation tool. If the firmware cannot keep the promise, the chart is not drawn.
02
Funnels across OTA
IoT App Analytics fails when “activation” resets after a silent firmware bump. We teach cohort windows that respect hardware reality, not mobile-only templates.
03
Two desks, one truth
Ops wants uptime; product wants habit. The studio forces both desks to share identifiers so Thailand-based fleets stop running parallel, incompatible stories.
Studio figures, not theatre
Numbers we actually keep.
18public cohorts since 2019, mostly evening sessions in Khlong Toei.
37hardware-product teams from Thailand and nearby ASEAN markets.
4.3instructor mark from 86 written reviews — not a perfect score, and we publish the caveats.
11weeks average between first scoping call and a stable telemetry contract.
Other desks
Shorter programmes when a full studio is too much.
Fleet Workshop
A clinic for teams who already ship a companion app and need funnel leakage diagnosed across two firmware lines.
Private instrumentation audit
On-site or remote reading of your MQTT topics and app events. We write the findings; you keep the backlog. Enquire via contact.
Field notes
Writing from the desk, not a content calendar.
Device funnels without vanity counts
Why “devices online” is a poor north star, and how to replace it with a funnel that still works after an OTA.
When MQTT payloads quietly drift
A Bangkok HVAC fleet lost three weeks of comparability because a boolean became a string. Here is the check we now run first.
If you are shipping hardware
Write to the desk. We reply within two working days.
Tell us which companion app, which firmware lines, and whether ops and product currently share identifiers. We will say honestly if Device Signal Studio is too heavy, or if Desk Notes is enough.