<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[🎨 Your First Dashboard in UI Studio]]></title><description><![CDATA[<h1>Your First Dashboard in UI Studio</h1>
<p dir="auto">UI Studio turns a product's data points into a mobile-style dashboard. No app build, no separate frontend project: you arrange widgets on a canvas, bind them to data points, and publish.</p>
<p dir="auto">This guide builds a small greenhouse screen with three values and one control.</p>
<p dir="auto"><img src="https://forum.grapesiot.com/assets/uploads/files/1794556172630-01-screens.png" alt="UI Studio workspace showing a product dashboard" class=" img-fluid img-markdown" /></p>
<p dir="auto"><em>The UI Studio workspace previews a product dashboard and opens the full editor in a new tab.</em></p>
<h2>Before you start</h2>
<p dir="auto">You need:</p>
<ul>
<li>a product with data points,</li>
<li>at least one device assigned to that product,</li>
<li>the device online or publishing (so you can see values move).</li>
</ul>
<p dir="auto">If you have not published a message yet, do the <strong>Quickstart: Device → MQTT → Live Monitor</strong> first. A dashboard with no data is hard to debug.</p>
<h2>1. Open the studio</h2>
<p dir="auto">There are two entry points:</p>
<ul>
<li><strong>From a product card:</strong> click <strong>UI Studio</strong>. This opens the studio for that product in a new tab.</li>
<li><strong>From the sidebar:</strong> open <strong>UI Studio</strong>, pick the product, then click <strong>Open in Studio</strong>.</li>
</ul>
<p dir="auto">The product-card route is the fastest way to start from scratch. The sidebar workspace shows the current dashboard and its component and effect counts.</p>
<h2>2. Know the three areas</h2>
<p dir="auto">The studio has three working areas:</p>
<ol>
<li><strong>Palette</strong> on the left: the widgets you can add.</li>
<li><strong>Canvas</strong> in the middle: a mobile-style surface at a fixed design width.</li>
<li><strong>Property panel</strong> on the right: the selected widget's settings.</li>
</ol>
<p dir="auto"><img src="https://forum.grapesiot.com/assets/uploads/files/1794556173761-03-widget-palette.png" alt="Widget palette in UI Studio" class=" img-fluid img-markdown" /></p>
<p dir="auto"><em>The palette groups widgets by job: controls, charts, UI basics, controllers, and effects.</em></p>
<p dir="auto">The palette groups widgets by job. You will use these groups most often:</p>
<ul>
<li><strong>CONTROL</strong> — toggles, sliders, input fields.</li>
<li><strong>CHARTS</strong> — line graphs and other history views.</li>
<li><strong>UI BASICS</strong> — text, meters, icons, shapes, colour pickers.</li>
<li><strong>CONTROLERS</strong> — scroll pickers, steppers, function sliders.</li>
<li><strong>EFFECTS</strong> — motion and other visual effects.</li>
</ul>
<p dir="auto">The exact list depends on your build. If a widget is missing, it may be a newer widget that is not enabled for your account.</p>
<h2>3. Add widgets</h2>
<p dir="auto">Drag a widget from the palette onto the canvas, or click it to add it at a default position.</p>
<p dir="auto">For the greenhouse screen:</p>
<table class="table table-bordered table-striped">
<thead>
<tr>
<th>Area</th>
<th>Widget</th>
<th>Bound data point</th>
</tr>
</thead>
<tbody>
<tr>
<td>Top</td>
<td>Text</td>
<td>none (title)</td>
</tr>
<tr>
<td>Row 1</td>
<td>Value / Status</td>
<td><code>temp</code></td>
</tr>
<tr>
<td>Row 1</td>
<td>Value / Status</td>
<td><code>humidity</code></td>
</tr>
<tr>
<td>Row 2</td>
<td>Line Graph</td>
<td><code>temp</code> (history)</td>
</tr>
<tr>
<td>Row 3</td>
<td>Toggle Switch</td>
<td><code>pump</code></td>
</tr>
</tbody>
</table>
<p dir="auto">Keep the canvas focused. A dashboard that shows everything is harder to use than one that answers a single question.</p>
<p dir="auto"><img src="https://forum.grapesiot.com/assets/uploads/files/1794556173188-02-canvas.png" alt="UI Studio canvas with dashboard widgets" class=" img-fluid img-markdown" /></p>
<p dir="auto"><em>The canvas is a mobile-style surface. Drag widgets from the palette, resize them, and bind each one to a data point.</em></p>
<h2>4. Style and layout</h2>
<p dir="auto">Select a widget to open the property panel. The tabs are:</p>
<table class="table table-bordered table-striped">
<thead>
<tr>
<th>Tab</th>
<th>What it controls</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>STYLE</strong></td>
<td>Colors, typography, borders, backgrounds</td>
</tr>
<tr>
<td><strong>LAYOUT</strong></td>
<td>Position, size, alignment, spacing</td>
</tr>
<tr>
<td><strong>LOGIC</strong></td>
<td>Data binding and behaviour</td>
</tr>
<tr>
<td><strong>EFFECTS</strong></td>
<td>State-based visual changes</td>
</tr>
</tbody>
</table>
<p dir="auto"><img src="https://forum.grapesiot.com/assets/uploads/files/1794556174353-04-property-panel.png" alt="UI Studio property panel tabs" class=" img-fluid img-markdown" /></p>
<p dir="auto"><em>Select a widget to edit its style, layout, logic and effects. Logic is where data binding lives.</em></p>
<p dir="auto">Use <strong>LAYOUT</strong> to align widgets to a grid. The canvas is mobile-first; keep touch targets large enough to tap and avoid placing controls at the very edge.</p>
<h2>5. Bind data</h2>
<p dir="auto">Open the <strong>LOGIC</strong> tab and find <strong>Data Binding</strong>.</p>
<p dir="auto"><img src="https://forum.grapesiot.com/assets/uploads/files/1794556174916-05-data-binding.png" alt="Data binding section in the Logic tab" class=" img-fluid img-markdown" /></p>
<p dir="auto"><em>Pick the device and data point in the Logic tab. The widget starts receiving live values as soon as the device publishes.</em></p>
<ol>
<li>Choose the <strong>device</strong>.</li>
<li>Choose a <strong>data point</strong>.</li>
<li>Confirm the widget supports that data point's type.</li>
</ol>
<p dir="auto">Binding rules to remember:</p>
<ul>
<li>A <strong>Status</strong> point can be read by a display widget.</li>
<li>A <strong>Control</strong> point can be written by a toggle, slider, or button.</li>
<li>A <strong>Both</strong> point can be read and written.</li>
<li>A numeric widget will not bind to a string point, and a boolean widget will not bind to a number.</li>
</ul>
<p dir="auto">If the data point list is empty, the device may not be assigned to the product, or the product may not have compatible points.</p>
<p dir="auto">For a line chart, bind history. If the data point does not have <strong>Storage</strong> enabled, there is no history to draw; the chart will be empty even though the live value updates.</p>
<h2>6. Add effects (optional)</h2>
<p dir="auto"><strong>EFFECTS</strong> lets a widget change its appearance based on a value. Typical uses:</p>
<ul>
<li>turn a status tile red when temperature is above a threshold,</li>
<li>change an icon when a pump is running,</li>
<li>show a warning state when a battery is low.</li>
</ul>
<p dir="auto">Effects are evaluated on the client from live values. They are not server-side automations. Use the <strong>Automation</strong> section if you need to trigger an action rather than change a visual.</p>
<h2>7. Publish</h2>
<p dir="auto">Click <strong>PUBLISH</strong> in the top bar. The current layout is frozen into a read-only screen.</p>
<p dir="auto"><img src="https://forum.grapesiot.com/assets/uploads/files/1794556175450-06-published.png" alt="Published read-only dashboard" class=" img-fluid img-markdown" /></p>
<p dir="auto"><em>PUBLISH freezes the current layout into a read-only screen that the device monitor and mobile clients can consume.</em></p>
<p dir="auto">The published screen:</p>
<ul>
<li>appears in the <strong>UI</strong> list,</li>
<li>can be opened in the studio for further editing,</li>
<li>is what the device monitor renders,</li>
<li>is read-only at runtime, so users cannot accidentally move widgets.</li>
</ul>
<p dir="auto">Publishing does not deploy firmware and does not change the data model. It only snapshots the layout and bindings.</p>
<h2>8. Verify with live data</h2>
<p dir="auto">Open the device monitor and publish a message. Confirm:</p>
<ul>
<li>the connection pill reaches <strong>Live</strong>,</li>
<li>each bound widget shows the expected value,</li>
<li>the toggle writes a control message when tapped,</li>
<li>the chart fills if history is enabled.</li>
</ul>
<p dir="auto">If a value is stale, check the binding first, then the payload key. A typo in <code>dpcode</code> is the most common cause of an empty widget.</p>
<h2>A good first-screen checklist</h2>
<ul>
<li>One clear purpose per screen.</li>
<li>A title that says what the screen is for.</li>
<li>The three or four values that matter most, not every value in the product.</li>
<li>Controls that are visually distinct from read-only values.</li>
<li>Large touch targets and consistent spacing.</li>
<li>A test with real data before you publish to users.</li>
</ul>
<h2>Common questions</h2>
<p dir="auto"><strong>Can I reuse a screen across devices?</strong><br />
Bindings are per widget. If devices share the same product and data point codes, you can copy the layout and change the device binding. Keep one screen per product family.</p>
<p dir="auto"><strong>Why is my chart empty?</strong><br />
The data point probably has <strong>Storage</strong> disabled, or the device has not published enough history yet.</p>
<p dir="auto"><strong>Why can't I bind a control?</strong><br />
The data point is probably <strong>Status</strong> only. Change it to <strong>Both</strong> or <strong>Control</strong>, or use a display widget instead.</p>
<p dir="auto"><strong>Does publishing affect the device?</strong><br />
No. Publishing only snapshots the dashboard. It does not send anything to the device.</p>
<h2>Next</h2>
<ul>
<li><strong>Data Point Types Explained</strong> for choosing the right widget and direction.</li>
<li><strong>Quickstart: Device → MQTT → Live Monitor</strong> for getting values into the platform.</li>
</ul>
]]></description><link>https://forum.grapesiot.com/topic/92/your-first-dashboard-in-ui-studio</link><generator>RSS for Node</generator><lastBuildDate>Thu, 19 Nov 2026 12:48:09 GMT</lastBuildDate><atom:link href="https://forum.grapesiot.com/topic/92.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 13 Nov 2026 07:49:32 GMT</pubDate><ttl>60</ttl></channel></rss>