App access

There is no separate headshot app to install

The headshot desk is an editorial website. The site does not publish a separate mobile app, does not maintain an APK, and does not ask a reader to install anything to read the desks. This page documents the device note and the spoof-app warning for the small number of cases where readers arrive at the desk from a third-party surface.

App access band illustration

Device note

How the headshot site works on phones and tablets

The headshot site is a responsive web property. On any modern phone or tablet browser, the site renders as a single-column mobile experience with a reachable hamburger, a sticky header, a single mobile play entry bar and a primary content flow that respects the editor's reading order. The site does not require a separate app install.

For the cleanest mobile experience, the desk recommends adding the site to the home screen as a Progressive Web App shortcut. That shortcut is offered by the phone's browser, not by the headshot brand. The shortcut opens the site in a dedicated window and keeps the editorial chrome intact.

For tablet and desktop, the site renders as a full editorial layout. The desk recommends a current-generation browser (Chrome, Edge, Firefox, Safari) and a screen width of at least 1024px for the cleanest reading experience. Older browsers still load the site but may not render all interactive elements correctly.

Spoof-app warning

What the desk does about third-party "headshot apps"

The desk does not authorise any third-party "headshot app" outside the central site. If you have arrived here from a third-party surface that asks you to install an APK or to grant unusual device permissions, the desk's recommendation is to close the surface and verify the URL bar.

The desk does not maintain an APK. The desk does not host the site on a third-party app store. The desk does not require a reader to install anything to read the desks. Any surface that asks the opposite is acting without the desk's authorisation.

For the small number of cases where a reader has installed a third-party surface by mistake, the desk's standard advice is to uninstall, run a security scan and reset any passwords that were entered on the third-party surface. The desk does not collect passwords, so the desk's password reset is not relevant.

Add to home screen

One-tap access without a separate app

iOS

Open headshotin.com in Safari, tap the share icon and select "Add to Home Screen". The icon will use the headshot favicon.

Android

Open headshotin.com in Chrome, tap the menu and select "Add to Home Screen". The icon will use the headshot favicon.

Desktop

Open headshotin.com in a current-generation browser, click the install icon in the URL bar and confirm. The shortcut opens in a dedicated window.

Device note

What "headshot app" means in three different contexts

The phrase "headshot app" can mean three different things. The first meaning is the headshot site, when a reader adds the site to the home screen on a phone. The shortcut is offered by the phone's browser, not by the headshot brand. The shortcut opens the site in a dedicated window and uses the headshot favicon as the icon.

The second meaning is a third-party "headshot app" that uses the headshot brand without authorisation. The desk does not authorise any such surface. The standard verification step is the URL bar and the certificate. If the URL is not headshotin.com, the surface is not a headshot surface, and the desk's recommendation is to close it.

The third meaning is a phone-based browser feature that bundles the headshot site into a navigation surface. The desk does not authorise this either, and the standard verification step is the same. The desk's editorial surface is the central URL, and the desk does not maintain any other surface.

Browser support

What a reader needs to read the desk on a phone

The headshot site is built as a single responsive web property. The site works on any modern phone browser without requiring a separate app. The minimum browser versions are the current generation of Chrome, Edge, Firefox, and Safari. Older browsers still load the site but may not render all interactive elements correctly.

The site's CSS uses standard media queries to collapse the editorial layout to a single-column reading flow at widths below 1000px. The site's JavaScript uses standard ES2017 features and the inert attribute. The site's fonts load from the public Google Fonts CDN with a preconnect for performance. The site's images serve from the central headshotin.com domain.

For the cleanest reading experience, the desk recommends a current-generation browser, JavaScript enabled, and a screen width of at least 320px. The site has been tested at 320, 347, 390, and 430px on both iOS Safari and Android Chrome, and at 1024, 1280, 1440, and 1536px on desktop. The desk publishes the verification result on the editorial review page.

Performance

What a current-generation phone needs to read the desk smoothly

The headshot site is built for current-generation phone browsers. The site uses standard CSS, standard JavaScript, and the public Google Fonts CDN. The site does not require a separate app, does not require a download manager, and does not require unusual device permissions. The site is reachable at the canonical URL on any phone that has a current-generation browser installed.

For the cleanest reading experience, the desk recommends a phone with at least 3 GB of RAM, a current-generation browser, and a stable network connection. The site has been tested at 320, 347, 390, and 430px on both iOS Safari and Android Chrome. The site has been tested on a five-year-old mid-range phone and renders the editorial layout correctly. The site has not been tested on feature phones, and the desk does not guarantee a clean reading experience on a feature phone.

For tablet readers, the site renders as a multi-column editorial layout at widths above 1000px. The site has been tested at 768, 834, 1024, and 1366px on both iPadOS Safari and Android Chrome. The site renders the desktop layout correctly at every tested width. The site has not been tested on a tablet that runs a non-current-generation browser, and the desk does not guarantee a clean reading experience on an older tablet.

For desktop readers, the site renders as a full editorial layout with a sticky header, a primary content flow, and a footer. The site has been tested at 1024, 1280, 1440, and 1536px on Chrome, Edge, Firefox, and Safari. The site renders the desktop layout correctly at every tested width. The site has not been tested on a non-current-generation desktop browser, and the desk does not guarantee a clean reading experience on an older desktop browser.

Phone features

Three phone features the desk uses, and one the desk does not

The first phone feature the desk uses is the home-screen shortcut. The site is built as a Progressive Web App; the phone's browser offers to add the site to the home screen on first visit. The shortcut opens the site in a dedicated window with the headshot favicon as the icon. The shortcut is offered by the phone, not by the desk, and the desk never asks the reader to install anything separately.

The second phone feature the desk uses is the back button. The site is built as a single-page navigation surface; the back button returns the reader to the previous desk. The site does not trap the reader in a modal flow. The site does not intercept the back button. The site respects the phone's navigation gesture and the phone's back button as a primary navigation tool.

The third phone feature the desk uses is the share button. The site offers a share button on every guide and every newsroom brief. The share button copies a canonical URL to the clipboard. The share button is a standard browser feature. The share button does not require a third-party widget or a third-party script.

The phone feature the desk does not use is the push notification. The desk does not ask the phone for permission to send push notifications. The desk does not maintain a proprietary notification surface. The desk's role is to publish reads; the reader's role is to read on the reader's schedule. The desk's editorial boundary on push notifications is the same as on every other intrusive surface: the desk does not authorise it.