Dev Browser

You can

• Type an address or a search in Search or enter URL and press the keyboard's Go key; the X (Cancel) stops editing.
• Reload with Reload; while a page is loading the same button becomes Stop.
• Open or close the DevTools panel with the </> button (DevTools). A red badge counts the errors in the console and stops counting at 99+.
• Open the Browser menu (⋮).

You can't, and why

• Load file://, content://, data:, javascript:, intent:, mailto: or tel: addresses: typed in the bar, they turn into a Google search.By design
• Choose another search engine: text that isn't an address is always searched on Google.By design
• Open plain http:// addresses on your local network (for example http://192.168.1.20): the app's network policy only allows unencrypted HTTP to localhost, 127.0.0.1 and 10.0.2.2. Use HTTPS or a tunnel.Needs network

You can

• Type the text in Find in page: it searches as you type, marks the matches in the page and shows how many there are.
• Jump to the next or the previous match with Next match and Previous match; the keyboard's Search key also goes to the next one.
• Close it with Close; that clears the search.

You can't, and why

—

You can

• Use the page as usual: scroll, tap, type and pinch to zoom.
• Pick files for a file upload field with the system file picker.
• See the page's own alert and confirm dialogs.
• Read load errors in a red toast you can copy: the WebView's own message, HTTP <code> <reason> when the page itself answers with 400 or above, or WebView render process crashed. Reload the page. A crash of the page's render process doesn't close PocketCode.

You can't, and why

• Follow links with other schemes (tel:, mailto:, intent:, file:…): they are ignored, with no message.By design
• Load HTTP content inside an HTTPS page (mixed content).By design
• Continue past an invalid TLS certificate, sign in with HTTP basic authentication or present a client certificate: the request is cancelled. Only the system's certificate authorities are trusted.By design
• Let a page use the camera, the microphone or your location: they are always denied, and the Console shows a Warning.By design
• Download files inside the app: a download link opens in the system browser.By design
• Open pop-up windows.By design

You can

• Filter by level with the four chips (error, warning, info, debug). Each shows its count; tap it again to remove the filter. There is no chip for plain console.log: you see those when no filter is on. The number on the right is how many messages are listed.
• Empty the console with the trash icon (Clear).
• Run JavaScript in the page's main frame: type it in Evaluate JavaScript… and tap Run. The command and its result (cut at 2,000 characters) are added as ordinary messages, so the filters apply to them.
• Bring back earlier commands with Previous command: it cycles through them and never repeats the same command twice in a row.
• Copy a message by pressing and holding its text.
• New messages scroll into view only if you were already at the end of the list.

You can't, and why

• See more than the last 1,000 messages: older ones are dropped. Navigating doesn't empty the console, but opening the Dev Browser on a different address does.By design

You can

• Filter by type with the chips All, Doc, CSS, JS, XHR (it includes fetch) and Img. Those words are always in English.
• Tap a request to open its detail below the list, with three tabs: General (url, method, status, size, time, duration and error), Request Headers (the headers the WebView hands over) and Response Headers.
• Empty the list with the trash icon (Clear).

You can't, and why

• See request or response bodies, response headers or the MIME type: the Response Headers tab always shows None, because nothing fills those fields yet.Not yet
• Break a request into DNS, TLS and waiting phases: each request has one bar, because the WebView doesn't provide those timings.Device
• Keep the list from one page to the next: it is emptied on every navigation of the main page (only the new document stays) and holds at most 1,000 requests.By design
• Count on a status for every successful request: it comes from the page's Resource Timing data, and when the WebView doesn't report it the column shows a dash. Error statuses (400 and above) always show.Device

You can

• Tap a row to open its full key and value in the detail below the list.
• Tap Copy to copy the value (Copied to clipboard confirms it).
• Tap Delete to remove that single key.
• Empty a whole section with the red clear icon next to its title (Clear).
• When the page has nothing, the panel says No storage data and suggests trying a site like google.com.

You can't, and why

• See HttpOnly cookies or the attributes of a cookie (domain, expiry, Secure, SameSite): the panel reads document.cookie, which hides them from page scripts.By design
• Delete a cookie that was set for another path or domain: deleting a cookie expires it with path=/.By design

You can

• Tap the selector icon (Select an element on the page), then tap anything on the page. The header says Tap an element on the page; your next tap picks the element without activating it (no link is followed and no form is sent), and the tree opens at that element, highlights it on the page and opens its detail below the list. If the element is deeper than the snapshot goes, it picks the deepest ancestor that is there.
• Read the snapshot again with Refresh DOM.
• Open a node's detail with its (i) icon (Entry details): its <tag>, its CSS selector and its id, class, attributes and text.
• Tap Copy selector to copy a positional selector such as html > :nth-child(2) > :nth-child(1); it uses positions, not ids or classes.
• Tap Highlight on page to outline the element in orange and scroll it to the centre. The outline stays until you highlight another node or reload.
• When nothing is loaded, the panel says No DOM tree and Load a page and tap refresh.

You can't, and why

• See the whole DOM: the snapshot stops at depth 10, 100 children per node (a … +N more node stands for the rest), 20 attributes per element, 500 characters of text and 200 characters per attribute value. It only holds elements (no comments) and it doesn't look inside iframes or Shadow DOM.By design

You can

• Write CSS in the editor (Editor) and tap Apply CSS: it creates, or updates, a <style> element with the id pocket-css-inject in the page.
• Remove what you applied with Clear (it is enabled only while something is applied).
• The last CSS you applied is applied again after every load, reload and navigation, even to another site, until you tap Clear. It is lost when you open the Dev Browser on a different address.
• Switch to Rules (n) to read the page's rules: the selector, the number of properties, the first three and where it comes from (the address of the stylesheet or inline). Tap a rule to copy its declarations into the editor; applying them then overrides the original instead of editing it in place.
• When there is nothing to list, the panel says No CSS rules detected.

You can't, and why

• See more than 200 rules, rules inside @media, @supports or @keyframes, or stylesheets the browser doesn't let a page read: only top-level rules are listed, and unreadable sheets are skipped without a message.By design

You can

• Read the cards under CORE WEB VITALS: First Paint (FP), First Contentful Paint (FCP), DOM Content Loaded (DCL) and Page Load always; Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS) and Total Blocking Time (TBT) when their value is above zero. Each card is coloured good, needs work or poor against fixed thresholds (for example LCP 2,500 and 4,000 ms, CLS 0.1 and 0.25, TBT 200 and 600 ms).
• Read PAGE STATISTICS: DOM Nodes, Resources and, when the WebView exposes them, JS Heap and Transferred.
• Read the RESOURCE WATERFALL (n): up to 50 resources with their type, the last 30 characters of the name and the duration.
• Tap Record: it reads the metrics again every 1.5 seconds until you tap Stop. It doesn't record a trace; it is a live refresh.

You can't, and why

• See the LCP, CLS and TBT cards when the WebView doesn't report them: they only appear when their value is above zero. The JS heap and the transferred size likewise depend on what the WebView exposes.Device

You can

• Tap Run Audit (it reads Auditing… while it runs). The audit only runs when you tap the button. Before the first run the panel says Run an audit to analyze page quality and Checks Performance, Accessibility, Best Practices, SEO and PWA.
• Read five gauges from 0 to 100 (Perf, A11y, BP, SEO and PWA; green from 90, orange from 50), the audited address and how long the audit took in milliseconds.
• Read the summary (N passed, N warnings, N failed) and filter with the chips All (n), passed, warnings and failed. A check passes at 0.9 or more, is a warning from 0.5 up to 0.9 and fails below 0.5.
• Fold the categories and open a check to read its detail (up to 8 lines).
• Tap the button again, now in the top bar, to measure again.

You can't, and why

• Get scores comparable to Lighthouse or PageSpeed Insights: these are PocketCode's own estimates, and some checks only look at a sample of the page (DOM depth reads the first 150 elements, font size 100 and tap targets 50).By design
• Inspect a service worker: the check only detects whether one controls the page.By design

You can

• Switch between the History and Bookmarks tabs.
• Tap an entry to open its address (it follows the same rules as the address bar) and close the dialog.
• Delete one bookmark with its trash icon (Delete).
• Delete the whole history with the red sweep icon (Clear), shown only on the history tab when there are entries. It asks for no confirmation.
• When a list is empty it says No history entries yet. Browse a few pages. or No bookmarks yet. Add one from the menu.

You can't, and why

• Keep more than 100 history entries or 200 bookmarks.By design

You can

• Edit Title, filled with the page's title (or its address), and URL, filled with the current address.
• Tap Save, which stays disabled while either field is empty, or Cancel. Bookmark added appears even if that address was already saved; it isn't saved twice.

You can't, and why

—

You can

• Tap Confirm or Cancel.
• On confirming, it clears the WebView's HTTP cache; the localStorage, the sessionStorage, the cookies visible to JavaScript and the IndexedDB databases of the open page's site; and all the cookies of the app's WebView, not only this site's. Then the Storage panel refreshes and Site data cleared appears.
• It keeps your browsing history: neither the page's back and forward history nor the History list is cleared.

You can't, and why

• Clear the data of just one site: the cookie wipe covers every site the app's WebView knows.By design