After a decade of AR projects, they built their own tool
The makers of Ordinary Objects turned recurring production and collaboration pain into a product others could try.
The takeaway
A recurring workaround can be the beginning of a product.
The context
The author described more than a decade of mixed-reality work and frustration with tool sprawl, client sign-off, and slow iteration. The product focused on the feedback loop between editor and device. A commenter still found the landing page unclear: building value and explaining it are separate tasks.
Steps worth trying
Editorial suggestions, not promises made by the original author.
- 01
Identify scripts or manual workarounds you repeatedly use in your work.
- 02
Watch peers perform the workflow to see whether the pain is shared.
- 03
Demonstrate the before-and-after workflow, then test willingness to pay.
Where this applies — and where it may not
A launch post establishes a product idea and development story, not profitability. Market size and customer acquisition costs still need validation.
From the discussion
“Your landing page doesn’t really explain the stuff you wrote here.”
@garyfirestorm · View source
Show HN: Making AR experiences is still painful – had to make my own editor
@boriskourt · 161 points · 27 comments
Read the Hacker News threadSource: OpenIndex Hacker News dataset (ODC-By). Original content belongs to its authors. Summaries, translations, and suggested steps are AI-assisted editorial work. Read the sources; individual outcomes are not guarantees.