Fire TV Implementation Options — Auto-load Welcome Screen (2026‑02‑05)

Goal: when the TV/Fire TV powers on (or the Fire TV reboots), it should open a web-based welcome screen automatically.

This doc focuses on pragmatic options from fastest to most robust.

Constraints to assume (validate per unit)

• Device could be Fire TV Stick or Fire TV built-in.
• Fire OS versions differ; Fire OS 8 has more restrictions around autostart/background behavior.
• Guests may press Home and leave the welcome screen; full kiosk lock-down is non-trivial on consumer devices.

Option 1 (fastest MVP): Digital signage player app that can show a URL

What: Install a signage player app from the Amazon Appstore that supports: - opening a website URL full-screen (or rendering content from a dashboard) - autostart on boot / resume after reboot

Pros - Fastest to pilot this week (minimal custom development) - Some providers include remote management, device fleets, monitoring

Cons / risks - Ongoing SaaS cost - You’re constrained by the app’s kiosk/URL capabilities - Some apps still require ADB tweaks on newer Fire OS

When to choose - 1–5 units, quick demo, minimal engineering.

Option 2 (recommended “quick but controllable”): Custom Fire TV app (WebView) that loads your URL

What: Build a simple Fire TV (Android) app that: - launches to a full-screen WebView - loads https://welcome.example.com/d/<token> - periodically reloads / handles offline

Then configure device so the app auto-starts after reboot.

Pros - Very aligned to “web-based welcome screen” (all business logic stays server-side) - Better control than Silk (no browser chrome; better crash recovery)

Cons / risks - Autostart on boot may require ADB permission hacks or OS-specific workarounds - Packaging, updates, and per-device setup overhead

Autostart approaches on Fire OS

Fire OS is Android-based, but Amazon updates increasingly restrict background launch at boot.

2A) ADB-based permission enabling (works for some signage players / may work for custom app) A known pattern (documented for some Fire OS 8 devices) is to enable developer options + ADB, then grant overlay/system alert permissions so an app can register autostart behavior.

Reference example (TrilbyTV guide): - https://kb.trilbytv.co.uk/activate-autostart-on-firestick-fire-os-8-devices

That guide’s key steps (high-level): 1. Enable Developer Options and ADB Debugging. 2. Find Fire TV IP address. 3. From a computer on the same network, connect with adb connect <ip>. 4. Run adb shell appops set <package> android:system_alert_window allow and grant overlay permission.

Notes - This is not an official Amazon kiosk API; treat it as best-effort and validate on the exact Fire OS + model. - Requires physical access and a laptop per unit (unless you standardize a setup rig).

2B) Make the welcome app the “launcher” (home replacement) - More kiosk-like: the welcome app becomes what Home returns to. - Harder on Fire TV; may require privileged settings changes and is brittle across updates.

2C) Use a “Launch on Boot” helper app - Some setups install a helper that launches a target app after boot. - Reliability varies by Fire OS version; may be blocked by OS updates.

Option 3: Silk browser “hack” (lowest engineering, higher UX risk)

What: Use Silk browser to open the welcome URL, and attempt to auto-launch Silk on boot.

Pros - No custom app needed

Cons / risks - Browser chrome / navigation elements can appear - Popups, cookie banners, autoplay restrictions - Hard to guarantee it opens the right URL after reboot - Guests can easily leave the browser

When to choose - Very short pilot, internal demo only.

Option 4: Screensaver-based approach (good as a fallback, not true “on startup”)

What: Configure a screensaver app or built-in screensaver behavior to display welcome images.

Pros - Easier to keep something visible when idle

Cons - Screensaver triggers on inactivity, not necessarily on power-on - Usually not interactive; may not render live web content

Option 5 (most robust, but heavier): Managed signage hardware / MDM

What: Use purpose-built signage devices or managed Android TV devices with kiosk mode.

Pros - True kiosk, remote device management, auto-recovery

Cons - More cost and more operational overhead

Practical setup checklist (for Phase 1 pilot)

1. Confirm device model + Fire OS version.
2. Decide guest experience:
   • Soft kiosk (welcome shows, but guests can leave)
   • Hard kiosk (must prevent leaving)
3. Build / choose the player:
   • Signage app with URL support, or
   • Custom WebView app
4. Configure autostart:
   • Try app’s built-in autostart setting
   • If Fire OS 8+ blocks it, validate ADB permission method (per device)
5. Disable power saving / screensaver interruptions where possible.
6. Verification test:
   • Power cycle TV + Fire TV 10 times
   • Confirm welcome loads within X seconds each time
   • Confirm it recovers from Wi‑Fi outage (unplug router for 2 minutes)

Inputs needed from James (Fire TV specific)

• Exact Fire TV models and Fire OS versions
• Whether we can:
  • enable Developer Options / ADB
  • keep devices on the same LAN (for setup)
• Desired lock-down level
• Whether guests should still be able to use Netflix/YouTube normally

Recommendation (quickest path)

• This week: Start with Option 2 (custom WebView app) + best-effort autostart, because it gives the cleanest “welcome URL” experience and keeps all logic server-side.
• If custom dev is too heavy for the week, choose Option 1 (signage player) as a stopgap and migrate later.