Creating Augmented Reality (AR) experiences remains a complex and challenging process. The author, frustrated with the limitations of existing AR development tools, built their own visual editor called Ordinary. It aims to simplify the workflow for building location-based AR experiences by offering an intuitive interface for managing assets, defining interactions, and previewing the final product in real-time. Ordinary emphasizes collaborative editing, cloud-based project management, and a focus on location-anchored AR. The author believes this approach addresses the current pain points in AR development, making it more accessible and streamlined.
The author of the blog post, detailing their project "Ordinary," expresses significant frustration with the current state of Augmented Reality (AR) experience creation. They argue that the available tools and workflows for building AR applications are cumbersome, inefficient, and ultimately painful for developers. This difficulty stems from a fragmented ecosystem of software, requiring creators to juggle multiple platforms and grapple with complex integrations. The author highlights the lack of a streamlined, intuitive process for designing and implementing AR experiences, particularly when aiming for sophisticated interactions and seamless blending of virtual content with the real world.
To address these perceived shortcomings in the existing AR development landscape, the author embarked on creating their own custom AR editor, "Ordinary." This bespoke tool aims to simplify and expedite the AR creation process, offering a more integrated and user-friendly environment. The post emphasizes a desire for fluidity and immediacy in AR development, suggesting that "Ordinary" enables rapid iteration and experimentation within the AR space. It is implied that this new editor offers a more direct and visual approach to crafting AR experiences, potentially abstracting away some of the technical complexities that burden developers using conventional tools. The ultimate goal, as articulated by the author, is to democratize AR creation and empower a broader range of individuals to build and share their own augmented reality visions. The launch of "Ordinary" is presented as a step towards achieving this ambition, providing a potentially more accessible pathway into the world of AR development. The author implicitly invites exploration and feedback on their creation, suggesting that "Ordinary" holds the promise of alleviating the pain points currently associated with building AR applications.
Summary of Comments ( 22 )
https://news.ycombinator.com/item?id=42838355
HN users generally praised the author's effort and agreed that AR development remains challenging, particularly with existing tools like Unity and RealityKit being cumbersome or limited. Several commenters highlighted the difficulty of previewing AR experiences during development, echoing the author's frustration. Some suggested exploring alternative libraries and frameworks like Godot or WebXR. The discussion also touched on the niche nature of specialized AR hardware and the potential benefits of web-based AR solutions. A few users questioned the project's long-term viability, citing the potential for Apple or another large player to release similar tools. Despite the challenges, the overall sentiment leaned towards encouragement for the author and acknowledgement of the need for better AR development tools.
The Hacker News post, titled "Show HN: Making AR experiences is still painful – had to make my own editor," sparked a discussion with several insightful comments. Many commenters sympathized with the author's frustration regarding the current state of AR development tools.
One commenter pointed out the difficulty of spatial computing, highlighting the challenge of representing real-world objects accurately in a digital environment. They mentioned how seemingly simple tasks, like aligning a virtual object with a real-world surface, can be surprisingly complex due to factors like lighting and texture. This reinforces the author's point about the pain points of current AR development tools.
Another commenter discussed their experience with different AR/VR platforms and the lack of standardization. They noted the fragmentation of the AR/VR ecosystem, with different platforms using various SDKs, making cross-platform development a significant hurdle. This commenter expressed hope for a more unified approach in the future, which would simplify the development process.
The high barrier to entry for AR creation was a recurring theme. A commenter lamented the complexity of existing tools and the steep learning curve involved, making it challenging for non-experts to create AR experiences. They suggested that simpler, more accessible tools are needed to broaden participation in AR development.
Some commenters also discussed the technical aspects of the author's custom editor. One commenter inquired about the specific features and capabilities of the editor, demonstrating interest in the author's solution to the challenges they faced. Another user discussed the potential benefits of using web-based technologies like WebXR for AR development, highlighting its cross-platform compatibility and accessibility.
Several commenters expressed appreciation for the author's work and shared their own experiences with AR development. The general sentiment was that while the author's experience of building a custom editor highlighted the current limitations of AR tools, it also showcased the ingenuity and resourcefulness of developers in the face of these challenges. The overall tone of the comments was one of shared frustration with the current state of AR development but also optimism for future improvements and innovation in the field.