Skip to content

ABOUT / DISCOVERY STANDARD

About BitShovel

Products and apps worth noticing, organized into clear profiles you can check against primary sources.

BitShovel focuses on the problem, current state, primary sources, and practical limits of each product so you can decide whether it deserves a closer look.

Why it exists

Product pages usually emphasize features and highlights while leaving stage, evidence gaps, and fit scattered. BitShovel brings those signals together so you can keep exploring, return to the source, or move on.

01

Product problem

Start with what it solves and who it is for.

02

Current state

Separate prototype, testing, review, live, and commercial stages.

03

Sources and limits

Return to primary material and mark what is checked or still uncertain.

Start with product value

Use the problem, core action, and intended audience to form the first judgment.

Then inspect evidence

Use sources, verification dates, and limits to keep promotion separate from conclusions.

Editorial and evidence standards

  1. 01Prefer creator posts, official project pages, and first-party documentation; search results are not evidence.
  2. 02Facts, editorial judgment, and next ideas are expressed separately so readers know the ground beneath each statement.
  3. 03Every capability is labeled by its real stage—concept, demo, usable, or released—and historical interfaces are identified.
  4. 04Never invent users, revenue, performance, partnerships, or usage claims; update or remove material that cannot be rechecked.
  5. 05Sponsorship, affiliate relationships, and other commercial ties must be disclosed at the top and do not alter verification standards.

Keep it current

Products change and judgments age. BitShovel keeps verification dates and revision paths so new facts can update old conclusions.

Keep following

Every new product record, project discovery, and verification update enters the RSS feed. Subscribe quietly and return when the next idea is useful.

RSS