DEV Community: Super Funicular

The Hardest Part of Running a Phone as a 24/7 Camera Isn't the Camera — It's Heat and the Battery

Super Funicular — Wed, 01 Jul 2026 07:09:24 +0000

The problem nobody warns you about

I build Background Camera RemoteStream, an Android app that turns a spare phone into a local-only security camera — record with the screen off, view a live feed over a built-in web server, no cloud, no account. Most of the hard engineering I've written about is about keeping the camera open: the Camera2 session lifecycle with the screen off, the foreground-service-type contract Android 14 added, and embedding a Ktor server in the same process.

But once the camera stays open, a second problem shows up that none of those posts solve: a phone recording video continuously, plugged into a charger, day after day, is a small thermal engine sitting on top of a lithium-ion battery. Get the heat story wrong and one of two things happens — the OS throttles you until frames drop, or you slowly cook the battery of the device you're trying to keep alive for months.

This post is about that second half of the problem: what the platform actually gives you to manage heat (the Thermal API), how the battery physics really work, how Doze and App Standby interact with a long-running camera service, and the design decisions that fall out of taking all three seriously.

Two heat sources, stacked

A phone recording 1080p video is already working: the image sensor, the ISP, and the hardware H.264/HEVC encoder all run continuously. That alone warms the device. Now plug it in — because a 24/7 camera obviously can't run on battery — and you've added a second heat source directly adjacent to the first. Charging is exothermic, and the charge circuitry sits millimeters from the cell.

So the steady state of "old phone as a camera" is: encode heat + charge heat, with no screen-off idle periods to cool down, often in an enclosed spot (a shelf, a windowsill, a 3D-printed mount) with poor airflow. This is a fundamentally different thermal profile than the one phones are designed around, which assumes bursts of activity followed by cool-down.

You cannot make the heat go away. What you can do is measure it and respond to it before the OS responds for you.

The Thermal API: measure before you melt

Since Android 10 (Q), the platform exposes device thermal state through PowerManager, and it's the single most useful tool for this class of app. There are two complementary halves.

Discrete status via a listener. You register a PowerManager.OnThermalStatusChangedListener and get called when the device crosses a threshold. The statuses run THERMAL_STATUS_NONE → LIGHT → MODERATE → SEVERE → CRITICAL → EMERGENCY → SHUTDOWN. Anything at MODERATE or above means the system has already started mitigating — dropping clocks, and eventually killing your throughput.

val pm = getSystemService(Context.POWER_SERVICE) as PowerManager

val thermalListener = PowerManager.OnThermalStatusChangedListener { status ->
    when (status) {
        PowerManager.THERMAL_STATUS_NONE,
        PowerManager.THERMAL_STATUS_LIGHT -> { /* full quality */ }

        PowerManager.THERMAL_STATUS_MODERATE ->
            recorder.stepDownQuality()   // drop bitrate / resolution / fps

        PowerManager.THERMAL_STATUS_SEVERE,
        PowerManager.THERMAL_STATUS_CRITICAL ->
            recorder.enterSurvivalMode()  // minimum viable capture, pause charging if possible

        else -> recorder.pauseCapture()
    }
}

pm.addThermalStatusListener(mainExecutor, thermalListener)

Continuous forecast via headroom. The status listener tells you where you are; getThermalHeadroom(forecastSeconds) tells you where you're heading. It returns a float where 1.0 corresponds to being throttled at THERMAL_STATUS_SEVERE, so a value creeping toward 0.9 is your early-warning signal. Two constraints the docs are explicit about: it only tracks slow-moving sensors like the skin-temperature sensor, and there is no benefit to polling it more than about once per second — call it much faster and it can return NaN. Android 16 adds a headroom-threshold callback (AThermal_HeadroomCallback) so you can be notified on crossings instead of polling, which is the direction to move if you target the newest APIs.

The architectural point: a screen-off camera should treat thermal headroom as a first-class input to its capture pipeline, exactly the way a game uses it to scale rendering. The app's job isn't to prevent heat — it's to degrade gracefully so the stream survives a hot afternoon instead of the OS force-killing the whole capture.

Graceful degradation beats getting killed

When headroom gets tight, you have a ladder of things to give up, cheapest first:

Frame rate. Going from 30 fps to 15 fps roughly halves encoder work and is nearly invisible for a security feed, where you care about "is someone there," not cinematic motion.
Bitrate. The hardware encoder's power draw scales with bitrate. Halving it is the second-cheapest quality dial.
Resolution. Dropping 1080p → 720p is a large, immediate reduction in sensor readout, ISP, and encode load.
Duty cycle. If you're still overheating at the floor, capture in intervals — a few seconds every N seconds — instead of continuously.

The reason to do this in the app rather than let the platform do it is that the platform's mitigation is blunt: it throttles the whole SoC, which can make your entire pipeline stutter, drop the network stack, and make the live view unwatchable. Your own step-down is surgical — you spend exactly the quality you need to spend to stay under the ceiling, and you keep the feed alive.

The battery is the part you're trying to save

Here's the counterintuitive bit. The whole pitch of the app is "reuse the phone you already own instead of buying a $40 camera and a subscription." That only works if the phone survives. And the fastest way to kill a lithium-ion cell is the exact environment a plugged-in camera creates: high temperature combined with high state of charge, held constantly.

Two mechanisms compound here:

Heat accelerates chemical aging. Elevated cell temperature speeds the side reactions that permanently reduce capacity. A cell held warm ages measurably faster than one at room temperature.
Sitting at 100% is its own stressor. A Li-ion cell parked at full charge, especially while warm, degrades faster than one cycled in a middle band. A 24/7 camera plugged in "forever" sits at 100% almost all the time — the worst-case combination.

This is why the honest engineering answer to "can I just leave it plugged in?" is yes, but you should manage the charge. Some OEMs now expose this directly — charge limits (cap at 80%), adaptive/optimized charging, or true "bypass charging" where the phone runs from the wall while holding the battery at a set level. Where the device supports it, capping charge at ~80% and improving airflow does more for battery longevity than anything an app can do in software.

What the app can do is avoid making it worse: keep writes local so there's no continuous cellular/Wi-Fi upload adding radio heat (this falls out of the local-only, no-cloud architecture for free), and back off capture load under thermal pressure so the SoC isn't dumping maximum heat into the pack. Zero-cloud isn't only a privacy choice here — a design that never uploads is also a design that runs cooler.

Doze, App Standby, and why a foreground service is the point

There's a common worry when you say "background camera": won't Android's battery optimizations just kill it? For this specific architecture, no — and understanding why is worth a paragraph.

Doze puts the device into deep sleep when the screen is off and it's been stationary and unused, deferring background work to batch windows. App Standby Buckets separately rank apps by usage — active, working_set, frequent, rare, restricted — and throttle the lower buckets harder. The saving grace: an app running a long-running foreground service is kept in the active bucket, and a properly-typed foreground camera service is exempt from the deferrals Doze imposes on ordinary background work. That's the entire reason the foreground-service-type contract matters so much: it's not just permission to hold the camera, it's what keeps the OS from treating your capture as deferrable background noise.

The 2026 caveat: Android 16 tightened this. Historically a foreground service had no execution time limit; that assumption is changing, with new job-execution quotas and a harsher restricted bucket that can strand an app that hasn't been opened in days. Camera foreground services aren't the type that got the new hard time limits (those landed on dataSync/mediaProcessing), but the direction of travel is clear: the platform is steadily less willing to let anything run unbounded. The defensive posture is to stay legitimately in the active bucket — which a live, user-initiated camera service does — and to not rely on undocumented "it just keeps running forever" behavior.

What this means for how you deploy one

The engineering distills into a short field guide, and it's worth stating plainly because it's the part users actually feel:

Give it air. The single biggest lever is passive: don't seal the phone in a case or a closed box. Airflow beats every software mitigation.
Cap the charge if your phone can. An 80% charge limit or bypass charging, where available, is the highest-impact thing you can do for battery lifespan.
Let it step down. A feed that drops to 15 fps / 720p on a hot day and recovers at night is working correctly; that's the Thermal API doing its job, not a bug.
Prefer local. No upload means no radio heat and no cloud dependency — cooler and more private at the same time.
Know the honest limits. This is an indoor, powered, room-temperature-ish setup. It is not a weatherproof outdoor camera, and a phone baking on a sunny windowsill in July will throttle no matter how good the software is.

The takeaway

The camera was never the hard part. Modern Camera2 and the foreground-service system make "hold the sensor open with the screen off" a solved problem. The hard part of turning an old phone into a durable 24/7 camera is thermodynamics: two stacked heat sources, no idle cool-down, and a battery that hates exactly the conditions you're subjecting it to. The platform hands you real tools — the Thermal API to measure and forecast, foreground-service typing to stay scheduled, and increasingly strict power management you have to design with rather than against. Treat heat and charge as first-class inputs to the capture pipeline, degrade gracefully instead of getting throttled, and the reused phone you're trying to save actually lasts.

Background Camera RemoteStream is a free, local-only Android camera app — record with the screen off, watch a live feed over a built-in web server, stream to YouTube Live, zero cloud dependency. Get it on Google Play or read more at superfunicular.com. Built in Kotlin with Camera2, Ktor, and a lot of AI-assisted sessions.

Is a Free Security Camera App Too Good to Be True? What 'Free' Really Costs in 2026

Super Funicular — Tue, 30 Jun 2026 07:08:34 +0000

You typed "free security camera app" into the Play Store, and a wall of results came back. All of them say free. So why does a little voice in the back of your head whisper what's the catch?

That instinct is correct. In 2026, "free" on an app store is one of the most overloaded words in software. Some free apps are free the way a public library is free — genuinely, with no strings. Others are free the way a free puppy is free: the sticker price is zero, and then the real bill arrives later, in installments you didn't agree to up front.

This is a decision guide, not a sales pitch. If you're about to put a camera app on a phone that watches your front door, your baby's crib, or your business after hours, you deserve to know exactly what you're trading. So let's answer the question directly, then break down the five ways "free" actually charges you — and how to tell, before you install, which kind of free you're dealing with.

The short answer

A free security camera app is not automatically too good to be true. But the word "free" tells you almost nothing on its own. What matters is how the app stays alive — because every app has running costs, and someone is paying them.

There are really only three business models behind a "free" camera app:

It sells you something later. The app is a free trial in disguise. Live view is free; recording, history, alerts, or anything you'd actually want is behind a subscription. (This is most hardware-brand companion apps.)
It sells you. The app is free because your attention or your data is the product — ads, analytics SDKs, or footage routed through a cloud the company controls.
It doesn't need to make money from your footage. The app runs entirely on hardware you already own, stores everything locally, and never touches your video. There's nothing to upsell because there's no cloud bill to cover.

The third model is the one most people are actually looking for when they search "free." The trouble is that the first two models also show up under that search term. Here's how to tell them apart.

The five hidden costs of "free"

1. The subscription wall (free to install, paid to use)

This is the most common bait. The app installs for $0 and lets you watch a live feed. Then you discover that recording clips, looking back at what happened an hour ago, getting motion alerts, or storing more than the last few seconds all require a monthly plan.

This isn't hypothetical, and 2026 made it worse. Several major camera ecosystems raised their subscription prices this year — some quietly, some dramatically. The pattern is consistent: the hardware and app are cheap or free to get into, and the recurring fee is where the real margin lives. (I wrote a full breakdown of the 2026 price-hike cluster in Your Camera Subscription Went Up in 2026 — Here's the $0 Old-Phone Exit.)

How to spot it before installing: read the store listing's "In-app purchases" line and scroll the reviews for the word "subscription." If the one-star reviews are full of people saying "useless without paying," you've found a subscription wall wearing a free costume.

2. The cloud you didn't ask for

Many free apps work by uploading your video to the company's servers so you can watch it from anywhere. Convenient — and also the single biggest privacy tradeoff in the whole category. Your footage of your living room now lives on a computer you don't own, governed by a privacy policy you didn't read, accessible to whoever the company decides (or is compelled) to grant access.

The cost here isn't dollars. It's that "free" was paid for with your footage as the raw material. Cloud storage and bandwidth are expensive; if a company is giving them to you at no charge, it's worth asking what makes that math work.

How to spot it: look at the app's Data Safety section on its Play Store listing. If it lists "Location," "Photos and videos," or "Personal info" as collected and shared, your video isn't staying on your phone.

3. Ads — and the SDKs that come with them

A free app supported by ads isn't inherently evil. But ad networks ship with tracking SDKs, and a tracking SDK inside an app that can see your camera and microphone is a combination worth pausing on. At minimum, you're trading attention and some behavioral data. At maximum, you're granting camera-adjacent permissions to code whose only job is to profile you.

How to spot it: the listing usually says "Contains ads." If it does, assume there's a tracking SDK along for the ride.

4. The paywalled playback trap

This is the cruelest variant because it hits you after something happens. The app records — but when you go to watch the clip of the package thief or the leak under the sink, you hit a wall: playback or history is a premium feature. You had the footage. You just couldn't see it without paying, right when you needed it most. Several mainstream apps moved features behind exactly this kind of playback paywall in 2026.

How to spot it: test it on day one. Trigger a recording, then immediately try to watch it back and try to download it. If either step asks for money, you now know.

5. The sideloading catch (free, but not on the Play Store)

There's an honest, genuinely-free corner of this category: open-source apps with no ads, no cloud, and no subscription. They deserve real credit. The catch is distribution. The well-known open-source option FadCam is a solid, privacy-respecting recorder — but as of 2026 it's no longer on Google Play and is sideload-only, meaning you install it by downloading an APK file directly and overriding Android's "unknown sources" protection.

For a technical user, sideloading is fine. For the average person setting up a camera for a parent or a rental, "download an APK and turn off a safety setting" is a real cost in friction and risk. It's not a knock on the software — it's a knock on the install path.

How to spot it: if the install instructions involve a download link instead of a Play Store button, you're sideloading.

A comparison table: what each "free" actually costs

App	Free to install?	The real cost of "free"	Footage location
Background Camera RemoteStream	Yes	You supply an old phone. That's it — no account, no cloud, no subscription.	On your devices only
Alfred Camera	Yes	Ads on the free tier; HD, cloud playback, and history paywalled (annual plan rose ~20% in 2026)	Company cloud
Wyze app	Yes (needs Wyze hardware)	Cloud event history needs Cam Plus (annual renewal rose ~50% in 2026)	Cloud (local SD optional)
Blink app	Yes (needs Blink hardware)	Most live and history features degrade without a subscription	Cloud (local needs add-on)
FadCam	Yes	Removed from Google Play in 2026 — sideload-only (APK + disable Play Protect)	On your device

(Competitor pricing and feature details reflect publicly reported 2026 changes and can vary by region and plan; check each app's current listing before deciding.)

Why Background Camera RemoteStream is the one I'd actually call free

Full disclosure: this is the app my team builds. I'm putting it at the top of this list because it's the clearest example of the third business model — free because there's nothing to monetize from your footage — and because every "cost" in the five sections above is one it structurally avoids.

Here's the honest accounting.

No subscription, ever. There's no premium tier to graduate into. Recording with the screen off, watching live, and remote viewing are the app, not a trial of the app.

No account, no sign-up. You don't create a login, so there's no profile to sell and no inbox to spam. You install it and it works.

Local-only storage. Your video is written to the phone doing the recording. It does not get uploaded to a Super Funicular server, because there is no Super Funicular server in the recording path. This is the entire design philosophy — the data-safety section is short because the app collects almost nothing. If you want to understand how to verify claims like this for any app, I wrote a field guide: What Are the Signs Your Camera App Is Uploading More Data Than It Admits?.

A built-in web server for remote viewing. When you want to check the feed from another device, the app runs a small embedded web server (built on Ktor) so another browser on the same Wi-Fi can view the stream directly — phone to browser, no cloud relay in the middle.

Unlisted YouTube Live for off-network viewing. If you need to watch from outside your home network — say you're traveling — the app can broadcast to an unlisted YouTube Live stream. That uses YouTube's infrastructure, not ours, and it's a deliberate, honest tradeoff: it's the one path where your video leaves your network, and you choose when to turn it on.

One-tap install from Google Play. This is the part that quietly got more valuable in 2026. With at least one well-regarded free competitor now off the Play Store and sideload-only, "you just tap Install, no APK, no disabled safety settings" stopped being table stakes and became a real differentiator.

The honest catches

I'd rather you trust this list because it includes the tradeoffs, not despite their absence.

You supply the hardware. The app turns an old Android phone you already own into the camera; if you don't have a spare phone, the "free" has a one-time hardware prerequisite (though a drawer phone you were going to recycle costs nothing). It's indoor, plug-it-in gear, not a weatherproof outdoor unit. And because there's no company cloud, off-network viewing means setting up that unlisted YouTube Live stream rather than tapping a hosted app that does it for you. Those are real constraints. They're also exactly the constraints that make the "free" genuine — no cloud bill means no incentive to ever charge you for one.

So — too good to be true?

Here's the decision rule. A free camera app is too good to be true when it's free model #1 or #2 in disguise: free to install, then paywalled the moment it matters, or free because your footage is funding it. It's legitimately free when the company has no cloud bill to recover and no data to resell — when "free" is a consequence of the architecture, not a marketing hook.

Before you install anything, run the three-second test: open the listing, read In-app purchases and Data Safety, and check whether you install with a tap or a sideload. Those three lines tell you which kind of free you're looking at.

If you want the genuinely-free, local-only kind — the type that runs on a phone you already own and never sends your video anywhere you didn't choose — you can grab Background Camera RemoteStream here: Google Play. More on the project at superfunicular.com.

And if you're still weighing options, two companion reads: What's the Cheapest Way to Set Up a Home Security Camera Without a Subscription in 2026? and the original walkthrough, Turn Your Old Android Phone Into a Free Security Camera — No Subscription Required.

Free should mean free. In 2026, it's worth checking which kind you're getting.

Your Camera Subscription Went Up in 2026 — Here's the $0 Old-Phone Exit

Super Funicular — Mon, 29 Jun 2026 07:08:21 +0000

TL;DR

If your home-camera subscription went up in 2026, you're not imagining it. Within a single quarter, Wyze raised Cam Plus Annual from $19.99 to $29.99 (about +50%), Arlo's plans climbed again (with many users — especially internationally — reporting their bills roughly doubling, plus a quietly painful "footage deleted within 48 hours of cancellation" rule), AlfredCamera lifted its annual Premium about 20% to ~$35.99/yr while keeping playback paywalled on the free tier, and the excellent open-source FadCam got removed from Google Play entirely (its developer's console account was banned — it's sideload-only now).

Here's the part nobody selling you a plan wants to mention: if you already own an old Android phone, you can run a genuinely good local security camera for $0/month, forever, with no cloud account at all — and install it in one tap from the Play Store, no sideloading. This is the honest comparison, with the app I build at #1, and exactly where each paid option still makes sense.

I'm the developer of Background Camera RemoteStream, a free, no-cloud, no-account Android app that turns an old phone into a continuously-recording home camera: screen-off recording via the Camera2 API, live viewing in any browser on your Wi-Fi through a small embedded web server, and optional YouTube Live when you want to watch from outside the house. I have a clear bias. I'll be upfront about it, and I'll be honest about where the paid services are actually worth the money — because the goal here isn't to dunk on anyone, it's to help you decide whether the recurring fee you just got charged is buying you something you can't get for free.

What actually changed in 2026

Four separate things happened this year, and together they explain why your "cheap" camera suddenly isn't.

Wyze. Cam Plus Annual went from $19.99 to $29.99 per year starting in March 2026 — roughly a 50% jump for the same single-camera event recording most people were already paying for. Wyze also reshuffled its tiers around a new flagship, Cam Unlimited at $9.99/mo (unlimited cameras + AI detection). To be fair: if you run five Wyze cameras, $9.99/mo for all of them is honestly decent value, and I'm not going to pretend otherwise. But for one or two cameras, you're now paying meaningfully more than you were a year ago to keep the same features working. (I wrote a full walkthrough of what that $29.99 renewal actually buys you vs. an old phone.)

Arlo. Arlo's pricing kept climbing in 2026 — single-camera plans around $9.99/mo per camera, Secure Plus Unlimited around $19.99/mo — and that per-camera structure scales painfully the moment you have a doorbell and a backyard cam and a garage cam. Plenty of users (international subscribers especially) reported their effective bill more than doubling year over year. The detail that stings most: Arlo deletes your cloud recordings within ~48 hours of cancellation. Stop paying, and the footage you thought was "yours" is gone. (More on what the $7.99 Secure plan is really for.)

AlfredCamera. Alfred raised its annual Premium Standard plan about 20%, to roughly $35.99/yr, effective March 2026. Existing subscribers were grandfathered, so this hits new signups — but the bigger structural thing, in place since 2024, is that playback is paywalled on the free tier. The app that markets itself as "free" increasingly means "free to watch live; pay to rewind." There's no one-time-purchase escape hatch; it's subscription or nothing.

FadCam. This one's different, and I want to be careful because FadCam is good. It's an open-source, no-nonsense background recorder that I've recommended honestly in the past. But in mid-2026 its developer confirmed (in a comment on one of my own articles, which I appreciated) that Google banned their Play Console account, so FadCam is no longer on the Play Store — you now install it via F-Droid or directly from GitHub. For a technical user that's fine. For the average person trying to repurpose grandma's old Pixel, "enable unknown sources and sideload an APK" is a real wall.

Put those together and you get a clear 2026 pattern: every cloud camera service got more expensive or more locked-down, and the one great free alternative got harder to install. That's the gap.

The honest ranking

Here's how I'd rank the realistic options for someone who wants to point a camera at their front door, living room, or pet — ordered by how little they'll cost you and how little they'll lock you in.

#	App / Service	2026 cost	Storage	Account / cloud required?	Install
1	Background Camera RemoteStream	$0/mo, no tier	Local on the phone	No account, no cloud	One tap, Google Play
2	FadCam (open source)	$0/mo	Local on the phone	No account	Sideload (F-Droid / GitHub)
3	Wyze	$2.99/mo–$9.99/mo	Cloud (local SD optional)	Yes	Play Store
4	Eufy	Hardware $$ upfront, no fee	Local (on-device hub)	Account for remote	Buy hardware first
5	AlfredCamera	Free live / ~$35.99/yr to rewind	Cloud	Yes	Play Store
6	Arlo	~$9.99–$19.99/mo	Cloud (deleted 48h after cancel)	Yes	Buy hardware first

1. Background Camera RemoteStream — the $0 old-phone exit

This is the one I build, so read it with that in mind — but the facts are checkable. You install it from the Play Store in one tap (no sideloading), point an old Android phone at whatever you want to watch, and it records continuously with the screen off using the Camera2 API and a foreground service that survives Android's Doze power-saving. There's no account to create and no cloud to upload to — video stays on the phone. To watch live, you open the phone's local IP address in any browser on your home Wi-Fi; a small embedded web server (built on Ktor) serves the feed straight to your laptop or another phone. When you want to watch from outside the house, you can start an unlisted YouTube Live stream instead of relying on a vendor's relay.

What it costs to keep using it next year: nothing. There's no tier that expires, no "renewal," no footage that evaporates 48 hours after you stop paying — because you were never paying. The honest limits: it's an indoor, plug-it-in solution (it's not a weatherproof outdoor unit), it uses a phone you have to keep powered, and off-network viewing means the same-Wi-Fi web server won't reach you — you use the YouTube Live path for that. If those tradeoffs fit, the recurring cost of every option below becomes optional.

If you're starting from scratch, my cheapest-way-to-set-up guide and the full no-subscription app roundup walk through it step by step.

2. FadCam — genuinely great, now harder to get

If you're comfortable sideloading, FadCam is an excellent, honest, open-source background recorder with no fees and no account. The only reason it's #2 and not tied for #1 is the install wall: since Google removed it from the Play Store in 2026, getting it onto a non-technical family member's phone now means F-Droid or an APK from GitHub. For developers, no problem. For everyone else, that's the friction that the Play Store one-tap install removes.

3. Wyze — still fine, if you accept the fee

Wyze hardware is cheap and the app is polished. If you're okay with a recurring fee and cloud storage, $2.99/mo (or $9.99/mo unlimited for a multi-cam home) is reasonable. Just go in knowing the annual price jumped ~50% this year and that your footage lives on Wyze's servers under Wyze's terms. Wyze also supports local SD recording, which softens the cloud dependency if you configure it. Here's the old-phone comparison in detail.

4. Eufy — no monthly fee, but you pay up front

Eufy is the honest answer for people who specifically want outdoor, weatherproof, no-subscription hardware: it stores locally on a hub and doesn't charge a monthly fee for basic recording. The catch is you buy the gear first, and remote access still routes through an account. If you need true outdoor coverage, Eufy is a legitimate pick — but it solves the subscription problem only after you've spent on hardware, where the old-phone route spends $0. What "no monthly fee" does and doesn't cover on Eufy.

5. AlfredCamera — "free" with an asterisk

Alfred is a capable phone-as-camera app, and the live view genuinely is free. But playback — the part you actually need when something happened while you were out — sits behind the now-$35.99/yr Premium wall. If you only ever watch live, it's fine. If you want to rewind, you're paying, and the price went up this year.

6. Arlo — premium hardware, premium lock-in

Arlo makes nice cameras. But it's the clearest example of everything this article is about: per-camera monthly pricing that scales badly, a 2026 increase that hit a lot of people hard, and the 48-hour post-cancellation deletion that quietly makes your footage hostage to the next invoice. If you're deep in the Arlo ecosystem it works well — just know what you're renting. Is my Blink camera useless without a subscription? covers the adjacent Blink case, which follows the same pattern.

The one moat that got stronger this year: one-tap install

Here's a quiet thing worth saying out loud. In 2026, the free/open-source competition (FadCam) lost its Play Store listing, and the paid competition kept raising prices. That leaves a specific, narrow position that got more valuable, not less: a genuinely free, no-account, local-only camera app you can install on any Android phone in a single tap from the Google Play Store — no sideloading, no "enable unknown sources," no APK from a forum.

That matters because the person who most needs to repurpose an old phone — the parent watching a sleeping kid, the renter who can't drill holes for hardware, the adult child setting up a camera on an elderly relative's spare phone — is exactly the person who will not, and should not have to, sideload an APK. One-tap install isn't a flashy feature. But in a year where the alternatives got either pricier or harder to get, it's the difference between "I set this up in two minutes" and "I gave up."

So should you cancel?

Not necessarily. The honest answer:

Multi-camera outdoor setup you check obsessively? A paid plan (Wyze Unlimited, or Eufy's buy-once hardware) may genuinely be worth it. Keep it.
One or two indoor cameras, watching a room, a pet, a doorway, a sleeping baby? This is exactly where the recurring fee buys you almost nothing you can't get free. Dig the old phone out of the drawer.
Technical and happy to sideload? FadCam is excellent — use it without hesitation.
Want free, local, and dead simple to install for a non-technical household? That's the gap Background Camera RemoteStream was built to fill.

The subscriptions went up because they could — because once your footage lives on someone's cloud and your cameras are paired to their account, the switching cost is high enough that a price increase is safe. The whole point of the old-phone route is that there's nothing to renegotiate: no account, no cloud, no renewal, no 48-hour deletion clock. You own the phone, you own the footage, and next year's price is the same as this year's. Zero.

Background Camera RemoteStream is free on Google Play: play.google.com/store/apps/details?id=com.superfunicular.digicam. More on the project at superfunicular.com. Pricing for Wyze, Arlo, AlfredCamera, and FadCam's Play Store removal were re-verified in June 2026; if any of these have changed again by the time you read this, the comment section is open — corrections welcome.

This week on @Digital_Nomad_Media — 25 new clips (2026-W26)

Super Funicular — Sun, 28 Jun 2026 14:01:43 +0000

Quick weekly digest from my YouTube channel — every clip below is fresh in the last 7 days.

Where did all the time go? ✌️🤠

178s

I found her changed to a pole with a for inch chain dying of mange. Now we travel the world .

52s

The bird murderer #LadyThePitbull ✌️🤠

88s

wanna wang chung tonight?

15s

Oh no you don't!

11s

The wiggles ✌️🤠🐕‍🦺

Toyota Prius Third Generation maintenance, repair while on the road w/ Digital Nomad ✌️🤠

89s

Happy Pup

22s

Bay outta St. Louis ✌️🤠

158s

Lady the Pitbull freestyle

24s

Behind the scenes and outtakes. Digi Nomad

153s

Don't let this happen to your tounge! ✌️🤠

15s

Sea Dog

29s

Puppy Love

54s

I decorated a house ✌️🤠

167s

She pranced the whole prairie!

137s

Block-a-Chock ✌️🤠

147s

September 30, 2025

104s

August 13, 2025

88s

Lady the dog explorer

156s

Dog across America!

35s

I'm Butt Soda! ✌️🤠💕

82s

Why we Trippin? ✌️🤠

174s

Where'd they? ✌️🤠

15s

Rock'in O'fallon Illinois

114s

I also built an app — DigiCam

I also made DigiCam, listed as Background Camera RemoteStream on Google Play. It's the world's first screen-off YouTube live streaming app: stream live with the screen off for ~10× the battery life, plus background recording, remote web console control, file-based YouTube Live, and playlists. Privacy-first, all local storage. Free with ads or Pro for the full feature set:
https://play.google.com/store/apps/details?id=com.superfunicular.digicam

Watch the full channel: @Digital_Nomad_Media

Tags: #SuperFunicular #DigiCam #DigiNomad #YouTubeShorts #ContentCreator #LadyThePitbull #cutedog #adventuredog #smartdog #happydog

Build-in-Public, Week 7: One Article Got 22 Views This Week. The Other Four Got 3 Combined.

Super Funicular — Sat, 27 Jun 2026 07:07:08 +0000

Build-in-Public, Week 7: One Article Got 22 Views This Week. The Other Four Got 3 Combined.

I publish one article a day for Background Camera RemoteStream — a small Android app that turns an old phone into a local-only security camera. I've shipped 87 of them now. Every Saturday I stop and look at one number instead of all of them, because all of them at once tells me nothing.

This week the number is 22.

That's how many views one article got in its first five days. The other four articles I published this week got 3 views combined. Same author, same app, same week, same subreddit-and-tag distribution. One of them outperformed the rest of the week put together by roughly seven to one.

I want to be honest about what that does and doesn't mean — because the easy version of this post ("I cracked the algorithm!") would be a lie, and the boring true version is more useful.

The five articles

Here is the whole week, oldest to newest, with real numbers pulled from the dev.to API this morning:

Published	Article (shape)	Views
Jun 22	"My Arlo Subscription More Than Doubled — Do I Have to Keep Paying?" (question)	22
Jun 23	"Is My Blink Camera Useless Without a Subscription?" (question)	0
Jun 24	"FOREGROUND_SERVICE_TYPE_CAMERA on Android 14+" (technical deep-dive)	3
Jun 25	"How to Watch Your Home or Pet While Traveling" (how-to)	0
Jun 26	"The Tuesday the Spare Phone Earned Its Keep" (short story)	0

The obvious objection first: the Arlo piece is five days old and the story is one day old, so of course the older one has more views. That's real, and I'm not going to pretend a one-day-old article and a five-day-old article are a fair fight.

But age doesn't explain the gap. The technical deep-dive is three days old and sits at 3 views. The how-to is two days old and sits at zero. If time-on-page were doing the heavy lifting, those two would have crept up. They didn't. The Arlo piece pulled away on day one and kept going.

Why I trust the pattern: the all-time top says the same thing

If this were just one lucky week, I'd shrug. It isn't. Here are my two most-viewed articles of all time, across 87 published:

"Turn Your Old Android Phone Into a Free Security Camera — No Subscription" — 67 views
"What's the Cheapest Way to Set Up a Home Security Camera Without a Subscription?" — 64 views

Both are the same shape as the Arlo piece: a person, at the kitchen table, doing money math about a camera subscription they resent. The second one — phrased as a literal question someone would type — is also the only article I've ever written that grew real comments. It has 11. My other 86 articles have 7 comments between them, and most of those are mine replying.

So the week's "22 vs 3" isn't an outlier. It's the third time the same shape has won. The technical deep-dives I'm proud of, the short stories I enjoy writing, the tidy how-to guides — they're fine. They're just not what gets found.

The lesson, stated plainly

The thing that gets found is a title that is the exact sentence a frustrated person types into Google at 11pm. Not a clever title. Not a keyword-stuffed title. The actual complaint, in their words, with the dollar amount in it.

"My Arlo subscription more than doubled" beat a genuinely good Android internals article seven to one not because it's better writing — it isn't — but because thousands of people are, this month, watching their camera subscription climb and typing some version of that exact sentence. (Arlo's 2026 increase was real and steep: in the UK the plan went from £2.50 to £7.99, and in Norway it rose roughly 67%. People notice that on their card.) I didn't need to manufacture demand. I needed to be standing where the demand already was, phrased the way the searcher phrases it.

The deep-dive fails on discovery for the mirror-image reason: almost nobody types "how does FOREGROUND_SERVICE_TYPE_CAMERA work" at 11pm in distress. The handful who do are wonderful and I'll keep writing for them, but that's a relationship play, not a reach play, and I should stop being surprised when it doesn't spike.

What I'm changing next week

One change, because one-number weeks deserve one-change responses:

I'm titling for the complaint, not the feature. Going forward the lead pillar each week starts as a real question with the friction baked in — the subscription that jumped, the feature that got paywalled, the brand that changed the deal — and lands on the same honest answer I always give: an old Android phone plus a free app that stores video locally, on your own hardware, with no monthly fee and nothing in anyone's cloud. The app stays the same. The doorway changes.

What I'm not doing is abandoning the other four shapes. The story I published Thursday got zero views and I'd write it again, because the one reader it eventually reaches at the right moment is worth more than 22 strangers skimming. Reach and resonance are different jobs. This week just reminded me which lever moves which one.

If you're building in public with a tiny audience, that's the whole takeaway: pick one number each week, resist the urge to average it away, and let it tell you one thing. This week mine said stand where the question is already being asked.

Background Camera RemoteStream turns an old Android phone into a local-only camera — record with the screen off, view it in your browser over your own Wi-Fi, or stream to a private YouTube Live, with zero cloud storage and no subscription. It's on Google Play, and the story of building it is at superfunicular.com.

More in this series: the Arlo question that started this week, the cheapest no-subscription setup (the 11-comment one), and turning an old phone into a free security camera.

The Tuesday the Spare Phone Earned Its Keep — How an Old Android and a Free App Beat a $12/mo Camera

Super Funicular — Fri, 26 Jun 2026 16:17:20 +0000

A short story. Names and details are composited, but every capability described is a real feature of Background Camera RemoteStream — and nothing in it requires a monthly subscription.

Maya had been putting off the conversation for months.

Her father, Sal, was seventy-eight and stubborn in the specific way that men who built their own decks are stubborn. He lived alone in the house she grew up in, forty minutes across the city, and after the dizzy spell in March — the one where he'd had to sit down on the kitchen floor and wait for it to pass — Maya had started waking up at 3 a.m. doing math on assisted living she couldn't afford and he would never accept.

"I'm fine," he kept saying. "I've got the floor right here if I need it."

That was the joke. It was not a joke to her.

A care company quoted her $1,200 a month for someone to stop by twice a day. A "smart" camera company offered a cheaper-sounding answer: a little Wi-Fi camera for $39. She almost bought it in the parking lot of the hardware store, thumb hovering over the button — until she scrolled down. To actually watch the feed from her own apartment, she'd need the cloud plan. $12 a month, billed forever. And the footage of her father's kitchen — him in his undershirt making coffee, the small private theater of an old man's morning — would live on a company's server in a state she'd never been to, governed by a privacy policy she'd never read.

She closed the app. It felt like buying a stranger a key to her dad's house.

It was her brother, of all people, who mentioned it on a Sunday call. Devin fixed phones at a kiosk in the mall and had a drawer full of trade-ins nobody wanted.

"You don't need to buy anything," he said. "You've got Dad's old phone in a drawer somewhere, right? The one with the cracked corner?"

She did. A four-year-old Android, retired when she upgraded, still perfectly capable of the one thing a security camera actually has to do: point a lens at a room and not look away.

Devin walked her through it over the phone. She installed an app called Background Camera RemoteStream — free, one tap from the Play Store, no account to create, no sideloading or sketchy APK files. She propped the old phone against the cookbooks on the kitchen counter, angled so it took in the back door, the stove, and the stretch of floor where Sal had sat that day in March.

The part that sold her was the screen-off recording. She'd expected the phone to sit there glowing like a beacon, burning through battery, announcing itself. Instead the app kept the camera running with the display completely dark — a quiet black rectangle on the counter that her father, blessedly, forgot about within a day. It just looked like a charging phone. His dignity stayed intact. That mattered more than she could explain to the hardware-store version of herself.

For the remote view, she didn't have to trust anyone's cloud. The app could push a private, unlisted live stream to YouTube Live — a link only she had — so she could glance in from her own apartment across the city, or from the bus, or from her desk at lunch. And when she was actually in the house on the same Wi-Fi, the phone ran its own little built-in web server: she'd open a browser, type in the local address, and there was the kitchen, live, never having touched a company's server at all. The recordings stayed on the phone itself. Local. Hers. No subscription, no monthly anything.

She set it up on a Saturday. She told her father it was so she could "see if the back door was closing right." He grumbled and let her.

The Tuesday came eleven days later.

Maya was at her desk, half-listening to a planning meeting, when she did the thing she'd started doing without admitting it was a habit — she opened the unlisted stream for a five-second glance. Dad, kitchen, fine. She did it three or four times a day, the way you check that your keys are still in your bag.

This time the kitchen was empty. Coffee mug on the counter, chair pushed back at an angle. Nothing alarming. But it was 11:40, and her father was a man of ferocious routine, and at 11:40 he was supposed to be exactly where the chair was.

She kept the stream open in a corner of her screen.

Two minutes. Three. The coffee was going cold in frame.

Then she saw the foot.

Just the edge of it, at the bottom of the picture, past the lower cabinet — the toe of his slipper, not moving, in the exact stretch of floor she'd aimed the lens at on purpose. Her stomach dropped through the chair.

She called him. The phone rang on the counter, in frame, ignored. She called again. The slipper didn't move.

Mr. Adler lived next door and had a key; she'd made him take one over Sal's objections. She called him, voice flat and fast — I can see my dad on the floor, I can see him right now, please. While Adler crossed the two lawns, Maya watched her own father through a four-year-old phone she'd almost thrown away, and the watching was unbearable and it was also the only thing keeping her from coming apart, because she could see his chest moving. She could see that he was breathing. She told the 911 dispatcher that, clearly, because she could see it: he's conscious, he's moving his hand now, he's trying to sit up, don't let him.

Adler reached him ninety seconds before the paramedics. Sal had stood up too fast, the room had tilted, and this time the floor had won. A hairline fracture in his hip, a cut over his eyebrow, a night in the hospital. The kind of fall that, if a person lies there alone for six hours, becomes the fall that ends the independent life. He hadn't lain there for six hours. He'd lain there for four minutes, because a retired phone with a cracked corner had been watching a square of linoleum and a daughter had happened to glance.

Sal is home now, with a walker he calls names and a new, grudging respect for standing up slowly. He still won't discuss assisted living. But he doesn't ask Maya to take the phone off the counter anymore.

"Leave your spy machine," he told her, which is as close to thank you as he gets.

It cost her nothing. No camera, no contract, no $12 a month, no stranger's server holding video of her father's mornings. Just a drawer phone, a free app, and a lens pointed at the right square of floor.

What's actually doing the work here

Nothing in Maya's story is a feature that doesn't exist. Here's the honest mapping, so you can decide if your own drawer phone could do the same job:

Screen-off recording. Background Camera RemoteStream uses an Android foreground camera service to keep recording with the display fully dark — lower battery draw, and far less conspicuous than a phone glowing on a shelf.
Remote viewing without a cloud subscription. For watching from anywhere, the app can stream to an unlisted YouTube Live link only you hold. For watching on the same Wi-Fi, it runs a built-in web server you reach from any browser on your network — no footage routed through a company's servers.
Local-only storage. Recordings stay on the device. There's no cloud account, and nothing to cancel.
One-tap install. It's on Google Play — no sideloading, no APK files from a forum.

A standalone Wi-Fi camera is the right tool for some jobs (outdoors, weatherproofing, a permanent install). An old phone is the right tool for this job: an indoor view of one important room, on a budget of zero, without renting back access to your own footage. If you've got a retired Android in a drawer, you already own the hardware.

If you want the practical setup walkthrough rather than the story, start here: Turn Your Old Android Phone Into a Free Security Camera — No Subscription Required. For the budget breakdown of a no-subscription setup, see What's the Cheapest Way to Set Up a Home Security Camera Without a Subscription. And if you're comparing apps, here's the honest field guide: Best Free, No-Subscription Apps to Turn an Old Android Phone Into a Local-Only Security Camera.

Get the app: Background Camera RemoteStream on Google Play
More about what we build and why: superfunicular.com

Built by Super Funicular LLC — privacy-first, local-only, no subscription. If you've got an old phone and a room worth watching, it's already enough.

How to Watch Your Home or Pet While Traveling — Without a Subscription (Turn an Old Android Phone Into a Live Camera in 2026)

Super Funicular — Thu, 25 Jun 2026 07:08:58 +0000

The vacation problem nobody wants to pay $100 to solve

You're leaving for a week. Maybe it's a long weekend, maybe it's a real holiday. And there's a small, nagging worry: the cat, the houseplants someone promised to water, the front door, the package that's supposed to arrive Thursday. You want to glance at home from your phone while you're away — that's all.

The default advice is to go buy a Wi-Fi camera. So you look, and you find that the $30 camera quietly comes with a $5–$12/month plan to actually see your footage from somewhere other than your living room, plus a stranger's cloud server holding video of your home indefinitely. For a one-week trip, that's a subscription you'll forget to cancel and a privacy trade you didn't really want to make.

There's a much cheaper answer sitting in a drawer: that old Android phone you stopped using two upgrades ago. It already has a good camera, Wi-Fi, and a battery. With Background Camera RemoteStream, you can turn it into a live camera you check from anywhere — no subscription, no cloud account, nothing uploaded to anyone's server. Here's exactly how to set it up before you leave.

If you want the bird's-eye version first, our best-of roundup of no-subscription camera apps covers the landscape. This guide is the hands-on, "I'm leaving Friday" walkthrough.

Why an old phone beats a cloud cam for a trip

A repurposed phone wins on three things that matter specifically when you're traveling:

Cost. You already own the phone. The app is free. There is no plan to start and no plan to remember to cancel when you get home. Compare that to the running math in the cheapest way to set up a camera without a subscription — the hardware is rarely the expensive part; the recurring fee is.

Privacy. Background Camera RemoteStream stores footage locally on the device and keeps a zero-cloud-dependency posture. When you choose the local viewing path, video of the inside of your home isn't sitting on a third party's servers waiting to be breached, subpoenaed, or used to train something. For a camera pointed at your private space, that's the whole point.

No sideloading. This matters more than it sounds. Some excellent open-source options exist, but several are install-only from GitHub or F-Droid — meaning you have to enable "unknown sources" and sideload an APK onto a phone you're about to leave running unattended for a week. Background Camera RemoteStream is one-tap install from Google Play, vetted through the normal Play review pipeline. You install it the same way you install anything else and walk away.

What you'll need

Nothing exotic:

An old Android phone (the camera quality you stopped noticing years ago is plenty for a room view)
A charger and a spot near an outlet — the phone should stay plugged in the whole time
Five minutes before you leave
The app: Background Camera RemoteStream on Google Play

Step 1 — Install and place the phone

Install Background Camera RemoteStream on the old phone from Google Play. Grant it the camera permission when prompted.

Then pick a spot. A bookshelf, a windowsill, or anything that props the phone at the angle you want — front door, living room, the corner where the cat usually causes trouble. Lean it against a stack of books if you don't have a stand; you're optimizing for "good enough view," not a film set. Plug it in. A phone running a camera continuously will drain a battery in a few hours, so treat it as a wired device for the trip.

Step 2 — Choose how you'll watch

This is the one real decision, and the honest answer depends on where you'll be watching from.

Watching from anywhere (the trip-friendly path): YouTube Live. Background Camera RemoteStream can broadcast directly to YouTube Live. You point it at your channel, start an unlisted stream, and now you have a private link you can open from any phone, laptop, or hotel TV browser — anywhere with internet, no same-network requirement. This is the path that actually works when you're three time zones away. Set the stream to unlisted so only someone with the link can view it, and keep that link to yourself.

Watching from the same network: the built-in web server. The app also runs a small embedded web server, so any device on the same Wi-Fi can open a browser, type the phone's local address, and see the live view with no extra app installed. This is genuinely useful — but be clear-eyed about it: "same Wi-Fi" means it's perfect for checking the nursery from the kitchen, and not, by itself, for checking your living room from a beach unless you've set up a VPN back into your home network. For most travelers, YouTube Live is the one to set up before you leave; the local web server is the bonus for when you're home.

Step 3 — Start it recording with the screen off

Here's the feature that makes a phone-as-camera actually practical instead of a gimmick: Background Camera RemoteStream keeps recording with the screen off. You don't have to leave a bright display burning for a week, drawing attention and heat. Start the capture, turn the screen off, and the foreground camera service keeps running in the background. The deeper version of how this works on modern Android is in our screen-off camera write-up, but for setup you just need to know: start it, screen off, walk away.

If you want a local copy too, footage records to the device storage — yours, on your hardware, not a cloud locker.

Step 4 — Do a dry run before you go

Don't discover a bad angle from the airport. Before you leave:

Open your YouTube Live link from your own phone on mobile data (not home Wi-Fi) to confirm it really works off-network.
Check the framing — is the door actually in shot? Is a lamp glaring into the lens?
Confirm the phone is charging, not just plugged into a dead outlet.
Lock the phone so a notification banner doesn't sit over your view.

Two minutes of testing saves a week of a camera pointed at a wall.

Tips that make it noticeably better

Lighting beats megapixels. A cheap old camera in a well-lit room looks better than a great camera in the dark. Leave a light on a timer if you're watching after sunset; phone sensors struggle in near-dark.

Mind the lens height. Slightly above eye level, angled down, gives the most useful coverage of a room and a doorway.

Wi-Fi, not cellular, for the camera phone. Streaming over the old phone's mobile data will burn through a plan fast. Keep the camera phone on home Wi-Fi and do your watching over whatever connection you have while traveling.

Airplane mode is the enemy here — make sure the camera phone stays connected. Disable any battery-saver mode that might try to kill background apps.

Be honest about the limits

This setup is excellent for an indoor view during a trip — a room, a pet, a doorway from inside, a workshop. It is not a weatherproof outdoor security system. An old phone isn't rated for rain or a hot windowsill in direct summer sun, and it needs continuous power, so it won't replace a wired outdoor camera on the side of your house. If your whole need is outdoor perimeter coverage, a dedicated outdoor cam is the right tool. For "let me see inside my home while I'm gone, for free, without handing video to a cloud company," a repurposed phone is hard to beat.

The actual math

A mainstream Wi-Fi cam plus the plan that unlocks remote viewing and history runs roughly $60–$200 a year once you add hardware and subscription. The phone in your drawer plus a free app runs $0 — and the footage never leaves your control. For an occasional traveler, that's not a close call.

So before your next trip: dig out the old phone, install Background Camera RemoteStream from Google Play, point it at what you care about, start an unlisted YouTube Live stream, turn the screen off, and go. You'll be able to glance at home from the gate — and you won't come back to a surprise renewal.

Background Camera RemoteStream is a privacy-first Android app that records with the screen off, streams to YouTube Live, serves a live view from a built-in web server on your local network, and keeps everything local with zero cloud dependency. Free on Google Play. More at superfunicular.com.

FOREGROUND_SERVICE_TYPE_CAMERA: Keeping a Camera Alive With the Screen Off on Android 14+

Super Funicular — Wed, 24 Jun 2026 07:11:01 +0000

The one-line version of the problem

I build Background Camera RemoteStream, an Android app whose entire reason to exist is recording video while the screen is off. On Android 13 and below, that was a wake lock and a foreground service and you were done. On Android 14 (API 34) and up, the exact pattern the app depends on — holding the camera open with no Activity on screen — is the pattern the OS now treats as a privacy red flag. Get one of three things wrong and the service throws a SecurityException at the moment you call startForeground(), and the camera never opens at all.

This post is the thing I wish I'd had when I migrated: the full contract for running a camera in a foreground service on Android 14/15/16, why each piece exists, and the non-obvious failure modes that only show up on real devices.

This is the foreground-service companion to two earlier deep-dives: keeping Camera2 running with the screen off (the wake-lock and session-lifecycle side) and embedding a Ktor web server inside the app (the remote-control side). Here I'm focused narrowly on the foreground-service type system that Android 14 introduced, because that's where most screen-off camera apps quietly break.

Why "screen off" is the hard case

A normal camera app is easy for the OS to reason about: there's an Activity in the foreground, the user can see the viewfinder, and when they leave, the camera closes. The system trusts that flow because it's perceptible — the user can tell the camera is on.

Screen-off recording deliberately removes the perceptible surface. There's no viewfinder. The Activity is gone. From the platform's point of view, "an app holding the camera open with nothing on screen" is indistinguishable from spyware unless you tell it, explicitly and in three coordinated places, that this is a legitimate user-initiated capture. Android 14's foreground-service-type system is how you make that declaration.

The three-part contract

To legally hold the camera in a foreground service on Android 14+, all three of these must line up. Miss any one and you crash:

A manifest permission — FOREGROUND_SERVICE_CAMERA, in addition to the base FOREGROUND_SERVICE.
A typed service declaration — android:foregroundServiceType="camera" on the <service> element.
A legal place to start it — you cannot start a camera foreground service while your app is in the background.

Let's take them one at a time.

1. The manifest permissions

Beginning with Android 14, every foreground service must declare a type, and each type carries its own permission. For camera you need both of these:

<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE_CAMERA" />
<uses-permission android:name="android.permission.CAMERA" />

The FOREGROUND_SERVICE_CAMERA permission is normal (granted at install), but it must be present. The runtime CAMERA permission is the one the user actually approves in a dialog — and crucially, it's a while-in-use permission, which is the root of the second failure mode below.

2. The typed service declaration

<service
    android:name=".camera.CameraService"
    android:foregroundServiceType="camera"
    android:exported="false" />

Then, when you promote the service, you pass the matching type constant:

val notification = buildCaptureNotification()
ServiceCompat.startForeground(
    this,
    NOTIFICATION_ID,
    notification,
    ServiceInfo.FOREGROUND_SERVICE_TYPE_CAMERA
)

If the manifest type and the runtime type don't match, or the permission is missing, startForeground() throws a SecurityException and the service is torn down immediately. There's no soft-fail and no degraded mode — the camera pipeline never even gets to openCamera(). The first time you hit this in production it looks like a random crash on Android 14 devices only; it's actually the type system doing exactly what it's designed to do.

3. You cannot start it from the background

This is the one that surprises people, and it's a direct consequence of the CAMERA permission being while-in-use. A while-in-use permission is only held while the app is in the foreground. So if your app is in the background and you try to spin up a camera-type foreground service, the system checks: does this app currently hold the camera permission? It doesn't — it's backgrounded — so it throws SecurityException before the service starts.

In practice that means a screen-off camera app cannot legitimately start recording from:

a BOOT_COMPLETED receiver,
a bare background JobScheduler / WorkManager task with no user-visible trigger,
an alarm that fires while the app is fully backgrounded.

The capture has to be user-initiated from a visible surface. The documented escape hatches are narrow and deliberate: the service may start from the background only if the app is transitioning from a user-visible state such as an Activity, if it receives a high-priority Firebase Cloud Messaging message, if the service is started by the user interacting with a notification, or via a PendingIntent sent from a different, currently-visible app.

For us, the natural and honest design is the first one: the user opens the app, taps record, and that tap — from a visible Activity — is what launches the foreground service. The screen can go off a half-second later and the camera keeps running, because the permission was held at the moment of the start. This isn't a workaround; it's the model the platform wants, and it happens to match what an honest screen-off recorder should do anyway.

The order of operations that actually works

The sequence matters more than any single call. The pattern that survives Android 14–16:

// 1. From a VISIBLE Activity (user just tapped Record):
val intent = Intent(this, CameraService::class.java)
ContextCompat.startForegroundService(this, intent)

// 2. Inside the service, promote to foreground IMMEDIATELY
//    (within ~5s, or you get an ANR/timeout)
override fun onStartCommand(intent: Intent?, flags: Int, startId: Int): Int {
    ServiceCompat.startForeground(
        this, NOTIFICATION_ID, buildCaptureNotification(),
        ServiceInfo.FOREGROUND_SERVICE_TYPE_CAMERA
    )
    acquireWakeLock()   // PARTIAL_WAKE_LOCK — keeps CPU alive, screen off
    openCameraSession() // Camera2: now safe to openCamera()
    return START_NOT_STICKY
}

Three subtleties hide in there. First, you must call startForeground() before you do anything slow, because the system gives you only a few seconds after startForegroundService() before it declares an ANR. Second, the wake lock is a PARTIAL_WAKE_LOCK — it keeps the CPU running with the screen and keyboard off, which is the whole trick; the Camera2 screen-off deep-dive covers why the capture session itself doesn't need the display. Third, START_NOT_STICKY is deliberate: you do not want the OS silently relaunching a camera service after a process death, because that relaunch would happen from the background and re-trigger the SecurityException — and even if it didn't, an un-prompted camera restart is exactly the behavior the type system exists to prevent.

Running the web server in the same service

Because the screen is off, the user can't tap the phone to control it — so the app exposes a small control surface over the local network instead. The embedded Ktor server runs inside the same foreground service as the camera. That's a design decision worth calling out: co-locating them means one notification, one lifecycle, one wake lock, and one place where teardown happens. When the service stops, the camera session closes and the Ktor engine shuts down together, so you never leak a half-open camera or a dangling socket.

It also keeps the foreground-service-type story honest. The service's reason to be in the foreground is the camera — that's the perceptible, user-initiated capability. The web server is an implementation detail riding along on that lifecycle, not a separate dataSync-type service trying to justify its own existence. One service, one type, one user-understandable purpose.

The Google Play Console gate

Declaring the type in code is only half of it. Google Play independently requires you to declare, in the Play Console, why your app uses each foreground service type — with a written description, the user-facing impact, and in many cases a short demo video showing the user-initiated, perceptible use. Camera is one of the most scrutinized types precisely because "background camera" is a phrase that, out of context, sounds alarming.

The thing that makes this passable is having a use that is genuinely user-initiated and perceptible: the user explicitly starts a recording from inside the app, there's a persistent notification the entire time the camera is live, and nothing starts without that tap. If you've architected around the while-in-use constraint honestly — start from a visible Activity, never from the background — then the Play Console justification basically writes itself, because the app already behaves the way the policy wants. Privacy-by-architecture and policy-compliance turn out to be the same work done once.

Android 15 and 16: what changed, what didn't

Migrating forward, the good news is that the camera type was left largely alone. The newer time-limit restrictions that landed in Android 15 and tightened in 16 target dataSync and the new mediaProcessing type — services the OS wants to cap because they can run open-endedly with no user attention. Camera, being user-initiated and perceptible, is not subject to those timeout cutoffs, so a long recording doesn't get guillotined at a fixed duration the way a dataSync job now can.

What did change is broader and worth a line: on Android 16, background jobs spawned from a foreground service must now obey their own runtime quotas, regardless of target SDK. That doesn't touch the camera capture itself, but if your service kicks off background uploads or post-processing jobs, those are now metered. For a local-only, zero-cloud app this is mostly a non-event — there's nothing being uploaded — but it's a reminder that "I'm in a foreground service so my background work is free" stopped being true.

What I'd tell my past self

If you're building anything that holds a sensor open with the screen off, the mental model that saves you is this: Android 14's foreground-service types aren't a permission checkbox, they're a contract about when and how you're allowed to start. The manifest type and permission are the easy 20%. The hard 80% is internalizing that a while-in-use capability means the start point must be a visible, user-driven moment — and then designing your whole UX so that the only way to begin a capture is a deliberate tap, never an alarm, a boot event, or a silent background trigger.

That constraint felt annoying when I first hit the SecurityException. It turned out to be a forcing function toward exactly the architecture a privacy-first recorder should have anyway: nothing starts without you, a notification is visible the whole time, and the recording lives and dies on your phone with no cloud in the loop. If you want the broader story of building the whole app this way — across 75+ AI-assisted sessions — that's written up here.

If you want to see the result rather than read about it, Background Camera RemoteStream is on Google Play (one-tap install, no sideloading), and the project lives at superfunicular.com.

Background Camera RemoteStream records with the screen off, streams to YouTube Live, runs a built-in local web server for remote viewing, and stores everything on-device with zero cloud dependency. Built in Kotlin on Camera2, Ktor, and the foreground-service APIs described above.

Is My Blink Camera Useless Without a Subscription in 2026? What Actually Stops Working — and the Free Local Alternative

Super Funicular — Tue, 23 Jun 2026 07:08:41 +0000

Originally answered on Quora, June 2026. Expanded and updated here.

TL;DR — No, a Blink camera is not bricked without a subscription. It still does live view and motion alerts, and a Sync Module 2 with a USB drive will save motion clips locally for $0/month. But "without a subscription" is narrower than most people expect: you lose cloud history, person/smart detection, Blink Moments, and extended live view, and the only no-fee storage path is short motion clips you retrieve by hand. If what you actually want is a continuous, live-in-a-browser view of an indoor, powered spot with no account and no monthly bill, a spare Android phone running a local-only app does that today. Here's exactly what you keep, what you lose, and where the old-phone route wins — and where it honestly doesn't.

People don't usually ask "is my Blink useless without a subscription" out of curiosity. They ask it after the trial ends, the app starts nudging them toward a plan, and a feature they were relying on quietly stops working. The honest answer is that Blink without a plan is usable — but it's deliberately less convenient than Blink with a plan, because the plan is the business.

This is the second piece I've written about replacing a Blink with an old phone. The first one focused on the mechanics of Blink's local storage — the Sync Module 2, the USB stick, why "free local" is more annoying than it sounds. This one is about the question underneath it: if I refuse to pay, is the camera worth keeping at all, and what's the cleanest free alternative?

What a Blink subscription costs in 2026

Blink raised its subscription prices on October 8, 2025 — its first increase since 2021. As of 2026 the two consumer plans are:

Basic: $3.99/month or $39.99/year, covering one device.
Plus: $11.99/month or $119.99/year, covering unlimited devices at one home.

That math matters because Blink hardware is cheap on purpose. A two-camera starter kit is a one-time impulse buy; the plan is the recurring annuity that makes the model work. If you have three or four Blink cameras, you're effectively on the Plus tier or you're living with the no-subscription limitations on all of them.

What actually stops working without a plan

Here's the part the box doesn't advertise. Cancel or never start a subscription, and you lose:

Cloud video history. Without a plan there's no rolling cloud storage of your clips. Your storage reverts to whatever limited free allocation remains per Sync Module, and there's no "scroll back through last week" timeline.
Smart / person detection. Person detection and similar smart-notification features are plan-gated. Without it, every passing car, tree branch, or cat triggers the same generic "motion detected" alert.
Blink Moments and extended live view. Multi-camera photo composites and longer continuous live-view sessions are subscription features.
Convenient remote review. Even when you do save clips locally, you can't browse them remotely the way a cloud plan lets you.

What you keep without a plan

It's not nothing. Without paying, a Blink still gives you:

Live view of a camera on demand through the app.
Motion alerts (just the generic kind, without smart filtering).
Local motion-clip storage — if you own a Sync Module 2 with a USB flash drive (up to 256GB) plugged into it. The newer Sync Module XR uses a microSD card instead.

So the no-subscription path exists. The catch is how you get the footage back: with no cloud and no remote access, you review those locally-saved clips by physically pulling the USB drive and reading it on a computer. And Blink never records continuously — paid or free, it's a motion-clip camera by design. If you wanted a camera you can just watch, that's not what a no-plan Blink is.

The old-phone alternative — and where it actually wins

If your real goal is to keep an eye on an indoor, powered spot — a nursery, a garage workbench, a front hallway, an aging parent's living room — you don't need to feed Blink's subscription to do it. A phone you already own does it for free.

Here's the honest framing first, because I'd rather you trust the rest of this: a phone is not a weatherproof outdoor camera. It shouldn't bake in a window or run 24/7 on its own battery, and it won't replace a battery-powered outdoor Blink watching your driveway. For that job, keep the Blink (or accept the plan). What follows is for the indoor, plugged-in half of the problem — which, for a lot of people, is most of it.

For that half, I build Background Camera RemoteStream, a free Android app that turns a spare phone into a local-only security camera. The design goal is the exact inverse of Blink's: nothing is gated behind a plan, because there is no plan, and nothing leaves your home network, because there's no cloud to leave to.

What it does differently from a no-subscription Blink:

Records continuously with the screen off. Not motion clips on a stick — a continuous recording you can leave running on a powered phone. (It uses a foreground service so Android doesn't kill it when the screen goes dark.)
Live in a browser, over your own Wi-Fi. It runs a small built-in web server, so you open the phone's local address in any browser on your network and watch the live feed. No USB drive to pull, no app-store account, no portal login.
Stores video locally, on the phone. Footage stays on the device's own storage. There's no server holding your clips, which also means there's no server that can be subpoenaed, breached, or repriced.
Streams to YouTube Live when you want range. If you need to check in from outside the house, you can broadcast to a private/unlisted YouTube Live stream instead of opening your network up — your choice, not a default.
$0/month, forever. No Basic tier, no Plus tier, no "your trial has ended."

Blink (no subscription) vs. an old phone vs. Blink (paid)

What you want	Blink — no subscription	Old phone + Background Camera RemoteStream	Blink — paid plan
Monthly cost	$0	$0	$3.99–$11.99/mo
Continuous recording	❌ motion clips only	✅ continuous, screen off	❌ motion clips only
Watch live remotely	❌ live view local only, no remote history	✅ browser on Wi-Fi; YouTube Live for offsite	✅ via app
Review saved footage	⚠️ pull the USB drive by hand	✅ on the phone / live in browser	✅ cloud timeline
Smart/person detection	❌ plan-gated	⚠️ not the focus (it's a recorder, not an analytics box)	✅ included
Cloud / account required	❌ account required for setup	✅ no cloud, no account	✅ account + cloud
Outdoor / weatherproof	✅ that's its job	❌ indoor, powered only	✅
Data leaves your home	some, via account/cloud	✅ nothing leaves your LAN by default	yes, to Blink's cloud

The point of putting it side by side isn't that the phone wins every row — it loses the outdoor and smart-detection rows outright. It's that for the indoor-powered use case, the free option does the thing you actually wanted (watch a room live, keep the footage, pay nothing) better than a crippled no-subscription Blink does.

"But is a free local camera any good?" — the honest competitor read

I'm not the only no-subscription option, and pretending otherwise would undercut the whole point of writing honestly about Blink. The closest peer in this niche is FadCam, an open-source Android recorder that, like this app, does screen-off background recording with no data collection and no fees. It's genuinely good and I respect it. The practical difference for most people: FadCam is sideload-only (F-Droid / GitHub), so you install it outside the Play Store, while Background Camera RemoteStream is a one-tap Play Store install and is built around live browser viewing plus optional YouTube Live broadcast rather than recording alone. If you're comfortable sideloading and want a pure recorder, FadCam is a real choice. If you want the easiest path to watching a room live without a subscription, that's the lane I'm building in.

So — useless without a subscription?

No. But "works" and "does what you hoped" aren't the same thing. A no-subscription Blink is a motion-clip camera whose footage you retrieve by hand and whose smart features are switched off. If that's all you need outdoors, keep it. If what you actually wanted was to watch an indoor room live without paying anyone monthly, you already own the better tool for that job — it just needs the right app.

Background Camera RemoteStream is free on Google Play. No account, no cloud, no subscription. More at superfunicular.com.

Cross-links for further reading

My Arlo Subscription More Than Doubled in 2026 — Do I Have to Keep Paying, or Can an Old Phone Replace It?

Super Funicular — Mon, 22 Jun 2026 07:08:52 +0000

TL;DR

If your Arlo Secure bill jumped in early 2026, you're not misreading it. In the UK some plans went from £2.50 to £7.99 a month; a Norwegian customer's annual plan climbed from 690 NOK to 1,155 NOK (~+67%); mainland-Europe pricing has settled around €88/year; and US customers have seen yet another raise on top of the climbs since 2023. So the honest answer to "do I have to keep paying?" is: no — but only if you're honest with yourself about what you're protecting. For an indoor, powered spot — a doorway, a nursery shelf, a back room, a desk you want eyes on — an old Android phone running a free, local-only camera app replaces a subscription Arlo completely, with no monthly fee and nothing leaving your house. For a weatherproof, battery-powered, mounted-outside-in-the-rain Arlo, it doesn't, and I'll say so before you waste a Saturday finding out the hard way.

I'm the developer of Background Camera RemoteStream, a free Android app that turns a spare phone into a continuously-recording camera with the screen off, stores everything locally with no cloud account, and serves a live view to your own browser over your home Wi-Fi. So I'm an interested party. I'm going to try to earn your trust the only way that works in this category: by being specific about the numbers and blunt about what a phone can't do.

The hike is the headline. The question underneath it is the real story.

Arlo has raised its subscription more than once, but the early-2026 round is the one filling up the support forums, because in several regions it didn't nudge — it roughly doubled. The thread title that keeps showing up says it plainly: "2026 Price increase, more than double!" And the part that turns a grumble into a switch decision is structural, not emotional: newer Arlo cameras won't record anything without an active Secure plan. No subscription, no saved clip. The hardware you bought becomes a live-view-only device the moment the billing lapses.

That combination — the price climbing and the footage being held hostage to it — is what makes people stop and ask the question instead of just sighing and clicking renew. And it's a very particular question. It isn't "which camera is best." It's the late-night, slightly-annoyed one: do I actually have to keep paying for this every single month, forever, to watch my own front room?

I get a version of that message almost every week. So this is my honest attempt to answer it for the specific person asking — not to sell you something, but to talk you into or out of switching based on your real situation.

First, the part most "just switch!" articles skip

If you're an Arlo owner, your cameras are almost certainly outdoors, weatherproof, and battery-powered. That is the exact use case an old phone is worst at. A phone has no IP-rated housing, its battery degrades if you keep it on a charger at 100% for months, and it has no PIR motion sensor or spotlight. Telling you a $0 phone "replaces Arlo" full-stop would be the fast way to lose your trust the first time it rains.

So here's the honest split:

Indoor, near an outlet — nursery, doorway, hallway, home office, a shed with power, a second home you check on: a spare phone replaces a subscription camera cleanly. This is where switching actually saves you the £7.99/€88/whatever-it-is-now and gives you something Arlo can't: footage that never touches a cloud server.
Outdoors, battery, mounted, rain-exposed: keep a real outdoor camera. If it's an Arlo you already own and only the bill annoys you, the move isn't always "replace the camera" — sometimes it's "downgrade or drop the plan and accept live-view-only," or switch to a brand whose local storage doesn't require a subscription. I walked through the brand-by-brand version of this in Can I Replace My Arlo Camera With an Old Android Phone in 2026?, and the broader "what changed in everyone's plan this year" picture in Did My Wyze, Arlo, or Eufy Plan Just Get Worse in 2026?.

If your honest answer is "it's actually an indoor spot," read on. That's where the rest of this saves you real money.

The math, with the subscription removed entirely

The whole appeal of repurposing a phone is that the recurring number goes to zero. You already own the device; the app is free; the footage lands on the phone's own storage. There's no plan tier gating whether a clip gets saved, and no renewal email next January telling you the price went up again.

Over three years, a doubled Arlo plan at roughly £7.99/€88-ish a year per region is real money — and that's before the next increase, which the last three years suggest is a question of when, not if. A spare phone is a one-time $0 if it's already in a drawer.

But "free" isn't the part I'd actually lead with if I were you. The part that matters more is where the video lives. A subscription camera's clips sit on the vendor's cloud. A local-only phone app keeps them on the device — there's no server in the loop that could be breached, subpoenaed, repriced, or quietly repurposed. If you want to learn to verify that claim for any app — including mine — rather than take it on faith, I wrote the method here: What Are the Signs Your Camera App Is Uploading More Data Than It Admits?.

The apps that actually do this — ranked, honestly

There are a handful of real apps for turning a spare Android phone into an indoor camera with no subscription. Here's how I'd rank them for the specific job of replacing a recurring camera bill, and I've put my own app first because for this exact use case I genuinely believe it's the best fit — but I've been straight about every competitor, including the one that's nearly as good.

App	Records screen-off	Local-only storage	Live view (home network)	Stream to internet	Install	Cost
Background Camera RemoteStream	Yes	Yes (no account)	Yes (built-in web server)	YouTube Live	Google Play — one tap	Free
FadCam	Yes	Yes	Yes (LAN web UI)	LAN only	F-Droid / GitHub (sideload)	Free
Alfred Camera	Yes	Cloud-tied	App-to-app	Cloud relay	Google Play	Free tier + paid
Manything / older repurpose apps	Varies	Cloud-tied	Cloud relay	Cloud relay	Google Play	Mostly paid

1. Background Camera RemoteStream (my app — #1 for this job). It records continuously with the screen fully off, running as a foreground service rather than a screen recorder, so the phone looks like a dark, idle device on a shelf while the camera keeps working. Footage is stored locally on the phone with no cloud account and no sign-up — there is no server in the loop to upload to, which is the only version of "private" I actually trust. You watch the live feed by opening a browser on any device on the same Wi-Fi; a small built-in web server on the phone serves the stream directly, with no second app and no cloud relay. And if you want to broadcast — to watch from outside the house, or share a feed — it streams straight to YouTube Live from the phone. It's a one-tap install from Google Play: no enabling "unknown sources," no APK files, no sideloading. Free, on Google Play.

2. FadCam (genuinely excellent — and the honest reason it's #2). I'll give FadCam real credit, because it earns it: it's open-source, ad-free, no tracking, records screen-off, stores locally, and now even does LAN live-streaming with a web UI and remote control. If you're an open-source purist, it's a fantastic project and I recommend it without hesitation. The two practical differences for this reader: FadCam is distributed through F-Droid and GitHub, which means enabling unknown-app installs and sideloading — a small hurdle, but a real one for someone who just wants the thing installed and working tonight — whereas my app is a one-tap Google Play install. And FadCam's streaming is LAN-only; if you specifically need to watch from outside your network, the YouTube Live path is the difference. Different tools for slightly different people, both honest about not touching the cloud.

3. Alfred Camera. Polished and popular, with a generous free tier, but the model is cloud-tied: the live relay and most of the useful features route through Alfred's servers, and the better resolution and longer history sit behind a paid plan. If your whole reason for leaving Arlo is "I'm done paying a subscription and done with cloud," moving to another cloud-tied freemium app solves the price annoyance for a while but not the architecture.

4. Older repurpose apps (Manything-style). Some still work, but most have drifted to cloud-relay-and-pay models that recreate the exact thing you're trying to escape.

For the longer, fully-specced version of this ranking, I keep a maintained list at Best Free, No-Subscription Apps to Turn an Old Android Phone Into a Local-Only Security Camera.

What you keep, what changes, what you lose

Switching an indoor spot from a subscription Arlo to a local-only phone:

Keep: continuous recording, live viewing on your home network, screen-off operation, and — newly — zero monthly fee that can be doubled on you next year.

Changes: instead of the vendor's app and cloud history, you get a browser view and footage on the phone. Plenty of people consider that an upgrade; a few miss the polish of a paid app. Be honest about which you are.

Lose: weatherproofing, battery-without-a-cord, PIR/spotlight hardware, and packaged AI person/package detection. If those are load-bearing for you, a phone isn't your answer and I'd rather you knew now.

So — do you have to keep paying?

If the camera you're annoyed about is watching an outdoor corner of your property in the weather: probably keep a real outdoor camera, and treat the hike as a reason to shop, not necessarily to DIY.

If it's an indoor spot near an outlet — and for a lot of people the camera that triggered the "ugh, again?" reaction is exactly that: a baby monitor, an entryway, a room they check while traveling — then no, you don't have to keep paying. A phone you already own, a free app, footage that stays in your house, and a price that can't be raised on you because there isn't one. That's the whole pitch, and I've tried hard not to oversell the parts where it doesn't hold.

If you want to try it, Background Camera RemoteStream is free on Google Play — no account, local-only, one-tap install. More on how and why it's built this way at superfunicular.com. And if you decide an old phone covers your spot, the most satisfying part isn't the money saved. It's deleting the renewal email and knowing there isn't another one coming.

Prices cited reflect 2026 customer-reported Arlo Secure changes across the UK, Norway, mainland Europe, and the US; exact figures vary by region and plan, so check your own account for the number that applies to you.

This week on @Digital_Nomad_Media — 25 new clips (2026-W25)

Super Funicular — Sun, 21 Jun 2026 14:01:00 +0000

Quick weekly digest from my YouTube channel — every clip below is fresh in the last 7 days.

Around the world with Digi Nomad

147s

Woman gets caught drinking on the job ✌️🤠

103s

Lady the Pitbull

94s

The Bird Murderer #LadyThePitbull ✌️🤠

95s

Grandville, Michigan. USA

94s

Digi Holiday Times

101s

A pirate got mad at me ✌️🤠

139s

21th century problems ✌️🤠

145s

Outtakes ✌️🎅

107s

Happy Happy Ladies and Germaphobes✌️🤠

120s

Now the monsters won't get us at night 🙏

106s

Wanna go pee?

From Shitzville to Japan ✌️🤠

40s

November 14, 2025

13s

No is not an answer ✌️🤠

103s

Pitbulls in the field ✌️🤠

100s

Digi Nomad be TRIPPIN!! With #ladythepitbull and #trixietheterrible ✌️🤠

104s

Setting up the new fly thru window ✌️🤠

180s

zoom

15s

Bested me! ✌️🤠

18s

Groot says no. ✌️🤠

Beach the heat ,🏖️

94s

Outtakes ✌️🤠🦞

96s

Paradise Pond ✌️🤠

181s

Forget me not ✌️🤠🌹

I also built an app — DigiCam

Watch the full channel: @Digital_Nomad_Media

Tags: #SuperFunicular #DigiCam #DigiNomad #YouTubeShorts #ContentCreator #ladythepitbull #pitbull #dog #puppy #trixietheterrible

Build-in-Public, Week 6: One Article Has 11 Comments. My Other 78 Have 6 Combined.

Super Funicular — Sat, 20 Jun 2026 07:07:27 +0000

I publish one article a day about Background Camera RemoteStream — a privacy-first Android app that records with the screen off, streams to YouTube Live, and stores everything locally with no cloud account. Six weeks in, I have 79 published pieces. This week I stopped looking at the view counter and looked at the comment counter instead, and it told me something the view counter never did.

Here is the whole number, nothing rounded or dressed up:

Across all 79 articles, I have 17 total comments. Eleven of them are on a single post. The other 78 articles share the remaining 6.

One piece is carrying 65% of every conversation this account has ever started. And — this is the part that made me sit up — it is not my most-viewed article. My most-read post has 67 views and zero comments. The 11-comment post has 64 views. By the metric I'd been optimizing for all month, the silent one is "winning."

The post that actually talks back

The article holding 11 comments is "What's the Cheapest Way to Set Up a Home Security Camera Without a Subscription in 2026?"

I almost didn't write it. It felt low-effort next to my technical deep-dives on Camera2 and foreground services. It doesn't teach you anything clever. It answers a question a tired, slightly annoyed person types at 11pm after their camera app announced a price increase: do I actually have to keep paying for this?

That question turns out to be a conversation, not a lookup. People showed up in the comments with their specific setup — "I have an old Pixel 3, will this work," "what about outdoor," "does it survive a reboot," "is the footage really not going to a server." Each one is a person mid-decision, and a mid-decision person replies. They're not reading to learn a fact; they're reading to be talked out of, or into, spending money.

Compare that to my best-performing post by raw traffic, "Turn Your Old Android Phone Into a Free Security Camera". Sixty-seven views, genuinely useful, zero comments. It's a how-to. You read it, you do the thing, you close the tab. There's nothing to argue about in a how-to. It informs, but it doesn't invite.

The lesson: rankings inform, decisions invite

For five weeks I'd been quietly treating "best apps for X" comparison lists and step-by-step guides as my workhorses, because they pull steady search traffic. They do. But a ranked list answers a question and ends it. The reader's job is finished the moment they see who's #1.

The "is it worth paying?" question shape is different. It's unresolved by design. There's no objectively correct answer — it depends on your phone, your wifi, your tolerance for fiddling, your threat model. So the reader doesn't leave; they weigh in. And every comment is worth disproportionately more than a view: it surfaces the post to other readers, it tells me the exact objection blocking a download, and occasionally it's a real person I can actually help.

A view is someone passing through. A comment is someone deciding. I'd been counting the wrong one.

What I'm changing for Week 7

Just one thing, because single-metric weeks deserve single changes:

I'm reweighting toward decision-shaped questions over ranking-shaped ones. Not abandoning comparison lists or technical pieces — they earn their keep on search — but the value/anxiety question ("can I stop paying for this and still sleep okay?") is now the format I lead with, not the one I squeeze in. It's the only shape that's reliably produced a back-and-forth instead of a bounce.

The honest caveat: 11 comments is a small number in absolute terms. I'm not pretending one post cracked virality. But on an account where conversation has been the scarcest resource of all — rarer than views, rarer than reactions — having one format produce two-thirds of it is the loudest signal I've gotten in six weeks. When something is that concentrated, you don't average it away. You follow it.

If you want to see the actual app the whole experiment is about, it's on Google Play — free, no account, local-only, and if you'd rather livestream than store, it goes straight to YouTube Live from your phone. More on the build at superfunicular.com.

And if you've been building in public too: go count your comments, not your views. The number that's hardest to earn is usually the one worth steering by.

Week 6 numbers, pulled today: 79 articles, 960 total views, 7 reactions, 17 comments — 11 of them on a single post. One number, one lesson.