# Node-RED dashboard interfaces - mobile vs tablet

**URL:** <https://discourse.nodered.org/t/node-red-dashboard-interfaces-mobile-vs-tablet/30349>\
**Category:** Dashboard\
**Created:** [19 July 2020 18:06 UTC](https://discourse.nodered.org/t/node-red-dashboard-interfaces-mobile-vs-tablet/30349 "2020-07-19T18:06:27Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [20 July 2020 11:51 UTC](https://discourse.nodered.org/t/node-red-dashboard-interfaces-mobile-vs-tablet/30349/6 "2020-07-20T11:51:41Z")

</div>

> [@alex88](#):
>
> It may be heaving going on the single Node-Red Pi supporting 4x devices.... is there a better setup you can suggest given the outcome I am looking for?

No, I often run multiple uibuilder instances on a single old Pi2 or Pi3 with lots of other things running. Performance will only start to suffer if you run too much on the Pi, run the Linux desktop on the Pi, have massive, complex flows (though some of mine are quite large) or try to send too much data too quickly.

> [@alex88](#):
>
> It may be heaving going on the single Node-Red Pi supporting 4x devices.... is there a better setup you can suggest given the outcome I am looking for?

Not, it will be fine as long as you aren't trying to update the interfaces on a millisecond basis. Typically I only update interfaces once a minute for home automation sensor outputs. You can do a lot more than that if you like but it rarely seems sensible in a home environment. Switches and similar controls happen ad-hoc of course without an issue.

One other thing to note. It is perfectly possible to build responsive interfaces that adapt nicely to different sized displays. The default libraries (VueJS and bootstrap-vue) that come with uibuilder make it pretty easy to build adaptive UI's so you might not actually need two different UI's.

> [@alex88](#):
>
> I guess the first approach would be to split into 2x Node-Red Pis if I hit performance issues: 1x Mobile interfaces and 1x Tablet interfaces???

Very, very unlikely you would need this complexity, especially with a 4GB Pi 4. You would have to be really loading up the Pi with tons of other services. Even my 512MB Pi2 runs some complex flows, Dashboard and several uibuilder instances along with MQTT, InfluxDB, Telegraf and Grafana. My 1GB Pi3 runs a similar stack and runs the Java-based Ubiquity Unifi Wi-Fi controller as well & that is a beast.

> [@bakman2](#):
>
> with uibuilder you will need to program this yourself

Yes, but the default libraries make this very simple. Very little, if any, additional code is required since the frameworks themselves are already responsive and adaptive and have sensible defaults.

> [@bakman2](#):
>
> uibuilder provides a communication interface to/from node-red, how you interact with it, you need to program yourself

That is true in that you need to deal with the incoming msg's in your front-end index.js file. The examples show how and the uibuilder library takes care of much of the complexity for you.

---

_[View the full topic](https://discourse.nodered.org/t/node-red-dashboard-interfaces-mobile-vs-tablet/30349)._
