StillWorks

The description states that StillWorks:

• Turns a seller claim into a short, agreed test plan.
• Uses browser APIs to observe device behavior (e.g., Gamepad API for controllers, MediaDevices for webcams).
• Produces a bounded condition card with PASS, FAIL, or UNKNOWN results.
• Operates entirely locally in the browser without backend services or account requirements.
• Includes a recorded fixture for judges without matching hardware.
• Exports evidence as JSON if desired.

Inference StillWorks is a browser-based tool that enables trust in second-hand electronics by testing specific device functions using web APIs. It avoids AI-generated verdicts and does not collect user data or require an account.

The description states:

• StillWorks aims to make trust a shared action at the moment of exchange, before money changes hands.
• It addresses uncertainty in second-hand electronics as a source of e-waste.
• The tool does not claim to certify devices; it records what one bounded handoff established.

Inference StillWorks positions itself as a lightweight, local-first solution for verifying device functionality during peer-to-peer transactions. Its core value is reducing uncertainty and increasing honesty in second-hand exchanges.

The description states:

• The tool targets buyers and sellers in second-hand electronics markets.
• It supports users who want to verify specific device functions before purchasing.
• It includes a judge path for those without matching hardware.

Inference StillWorks appears aimed at individuals or small groups involved in peer-to-peer electronics sales, particularly where trust is a concern. The ICP likely includes tech-savvy users comfortable with browser-based testing and minimal setup.

The description states:

• There is no mention of pricing.
• No business model is described beyond the tool’s functionality.
• It is built as a static PWA with no backend or monetization layer.

Inference There is no evidence of a business model or pricing strategy. The product appears to be a prototype or proof-of-concept, not a commercial offering.

The description states:

• Built with Next.js, React, and TypeScript.
• Fully static production export.
• Uses browser APIs for testing (Gamepad API, WebAudio, MediaDevices).
• Implements deterministic test planning.
• Includes a PWA shell, export flow, tests, and documentation.
• No backend, analytics, or runtime model verdicts.

Inference StillWorks is technically a local-first, static web application with no external dependencies. It uses browser APIs to perform device-specific tests and avoids AI-generated outcomes in favor of deterministic code-based results.

The description states:

• The project was built during a hackathon.
• No revenue, customers, or adoption data are provided.
• The tool is described as a complete prototype with 12 deterministic and integration tests.
• It includes clean-build, browser, security, and accessibility checks.

Inference There is no evidence of traction, revenue, or customer adoption. The project appears to be an experimental prototype, not a mature product in use.

The description states:

• No mention of competitors.
• The tool focuses on local testing and avoiding AI-based verdicts.
• It emphasizes honesty in reporting uncertainty (UNKNOWN) over false positives.

Inference No competitive landscape is described. StillWorks appears to be a unique approach to device verification, but its positioning against existing tools or platforms is not evident from the description.

The description states:

• The tool does not claim to certify devices.
• It avoids backend services and AI runtime decisions.
• It includes a recorded fixture for judges without matching hardware.

1. Has StillWorks been tested in real-world second-hand transactions?
2. Are there any plans to monetize the tool or integrate it into existing marketplaces?
3. How does StillWorks handle edge cases like browser permission failures or hardware unavailability?
4. What is the long-term vision for expanding device categories and test types?
5. Is there a plan to move beyond the static PWA model, or is this intentional?