Limits of the published build
What exists only in development builds, what is off in the installed app, and what is not an available path.
Not every Browser feature is available in the installed app. This page separates three cases that are often mistaken for defects.
Browser developer tools
The button that opens the page inspector and the equivalent menu item only appear in development builds. In the installed app they do not exist — and that is expected, not a hidden feature.
Practical consequence: in the installed app, the page inspector is not available. On a development build, the button opens the embedded browser’s tools.
Automatic app preview
The surface that would offer to:
- detect the project’s development server without configuration;
- turn the project’s app on with one click;
- announce when the app just changed;
is off in the installed app and is not a product feature today.
What the Browser screen does without it: it is a browser. The empty state asks you to open a page, and the new-tab button and the address bar stay in place.
Do not count on automatic server detection or automatic page refresh.
Phone remote control
The gesture that hands the tab’s control to a phone and shows the notice that the device is driving the browser is not an available path in the installed app.
Related
- The Browser screen
- Pointing and sending to the agent — the pointing surface is on, and does not depend on the preview