The fact that the Starling's main access point for most of the configuration and monitoring is its internal web server makes it conveniently accessible across devices without need for apps and wirelessly. However, like with everything, this system isn't entirely bulletproof, and some limitations associated with the usage of a third-party browser (whichever one you may choose) are unavoidable.
For example, the Starling's tab has to be focused for it to continue sending requests to the device consistently, as browsers may otherwise sleep the tab to save energy. In many cases this won't matter, but if you wish to remain an active client and you're using the web server (whether it be the public panel or one of the sentinel-only pages), you'll need to keep this in mind.
Browsers also have a tendency to cache the contents of pages to save time and avoid having to load it all every time. This is mostly fine, but in situations like after an update, to ensure the contents (and backend functionality!) of the pages are consistent with the current version, you will need to force a reload of the page (hold the Shift key and press the reload button).
Another thing to keep in mind is that name changes take a long time to propagate, as mentioned in the configuration page section. This will hardly be an issue, as changing the name of the unit is something that usually is done just once at the beginning of its life, but it's noteworthy to prevent confusion when the changes take a long time to take effect.