-
-
-
Optomole Platform
Inspiration
The Inspiration behind Optomole was simply an small ideal which started with a desire to actually make doing remedial, mundane tasks fun, using gamified quests Optomole was born. The ideal what if you could enjoy going through your email inbox and not only clearing it out but actually extracting what you needed from each message, what if you could actually get through that clutter of newsletters, or e-courses, well now with Optomole you can.
What it does
Optimole works by generating aesthetically pleasing futuristic interactive playable progressions ,to interact with everyday mail, files, newsletters, etc which then turns your content from those ingested emails into game quests of your desired genre type. Various game play types to choose from which Optomole matches with you your content and your desired productivity goals.
How we built it
Optomole is, was, and still being built out by a one man team utilizing Codex and OpenAIs new model GPT5.6, with a tech stack of React for the front and backend. Optomole is broken up into services which can be run together to create a full Content to Game Engine Platform, or as a plugin, SDK, API, worker, etc. The main power behind Optomole is not creating games but taking text and real world data and compiling that info into storyboarded, real world experience files to feed into any LLM of your choosing to produce an ExperienceManifest.json to feed into nearly any Game Engine of your choice; Unity, Unreal Engine, etc so those engines can have all the ingredients it needs to create you a genuine interactive game.
Challenges we ran into
The ideal took a lot of twists and turns, and due to limited time it boiled down to simply creating a POC or proof of concept, as attempting to make Optomole a game creation engine itself was not feasible with the limited time and resources, so focusing on making Optomole an content to experience engine where users content would be highly structured and tuned for what I call an IRX, having several small engines feed into it such as the semantic extraction engine, the normalization engine, the storyboard engine, and others all to create an ExperienceManifest.json this was difficult because each of the engines needed to be custom built and fine tuned to attempt to avoid stale and repeatable output from the different LLMs, also not having time to create a multitude of game templates, left me at a pass where I had to settle for simple boiler plate games which do not do the content to experience engine much justice, which is why at this point Optomole is simply a POC.
Accomplishments that we're proud of
Being able to start a project and deliver something within a deterministic time period, which still represents the vision, and potential of the program.
What we learned
That there are tons of resources available on and offline, when you get into a grove the Universe just seems to send these resources your way and things flow, this project was hard coded and vibe coded, maing that a challenge in itself but truly learned that working with AI Agents can truly reduce the time required to complete workloads.
What's next for Optomole
Optomole, will continue to hone and fine tune the Experience engine through users usage, so that the storyboarded game play will be much more sophisticated, more highly custom to user and their data, and the games will become more unique, which at some point may even potentially create a marketplace of their own.
Log in or sign up for Devpost to join the conversation.