Health, home and travel decision

Sabbath Space

A basic Android-only app triggered by a Bluetooth/NFC tag is realistic for a single technical builder, but full parity with the paid product (especially iOS behavior and shipped hardware/fulfillment) is not achievable without vendor hardware, platform-level controls, or extra operations.

Visit website
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off100 h to build

$20/mo3 h/mo upkeep

No published price to break even against.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Sabbath Space alternatives, with the arithmetic →

What a replacement has to do

  • User taps a Bluetooth tag which the mobile app detects; the app enforces a restricted phone mode that blocks selected apps/notifications; user can configure which apps remain available.

What it still won’t have

  • Official hardware manufacturing, fulfillment, and quality control
  • Polish and cross-platform support (iOS parity) provided by vendor
  • Integrated physical-device warranties and logistics
  • Any proprietary firmware or closed integrations the vendor supplies (if any)

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Sabbath Space does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal Android-first implementation using Kotlin, Firebase, and a small Node.js hosting tier: 1) Implement an Android app with an AccessibilityService and a local settings UI to choose allowed apps and enable/disable a 'locked' mode; 2) Add Bluetooth LE (and NFC fallback) tag pairing and detection to trigger lock/unlock; 3) Store user settings and simple usage events in Firebase (Auth optional, use anonymous or email login); 4) Provide a small Node/Express endpoint for analytics and a static Shopify or Netlify landing page for hardware orders; 5) Include error handling for Bluetooth failures, permission denial, and AccessibilityService stop/restart; write unit tests for core app logic and end-to-end tests for lock/unlock flows. Out of scope: iOS implementation, manufacturing or shipping workflows, and MDM-based enterprise controls.
How we checked4 sources · 3/3 runs agreed · evidence score 64

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 cited sources+3
  • 3/3 assessment runs agreed+4
  • Evidence score64

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 4

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded