do have a question about that right in a sense like what do you build how to prioritize but before this right after seeing all this and maybe you can indeed let's say for now stop sharing um but what would you position story splat between let's say a 3d engine and and a google slide tool

uh yeah so i like to place it somewhere Cleanly in the middle, more leaning towards Google Slides, if anything, like maybe 60% of Google Slides, 40% of more of a traditional 3D engine.

The idea is to give people access to as many of the tools that they need from those 3D engines to tell a story natively on the web, but to also keep it as accessible as possible where they can do so without writing any code.

They don't need experience in these engines.

A lot of the actual... um inspiration for for doing this all came from students and journalism so like my background for spatial storytelling was doing photogrammetry as a research assistant my senior year at Syracuse University and we told like a really compelling story that won a bunch of awards so like that's the core of what I'm aiming for and it's since you know bifurcated to some some different um verticals I'd say and you know you have the real estate side and you have the more like Yeah, cultural preservation side, but then journalism is is where like the passion sort of is.

And journalists don't really know how to use 3D editing tools usually.

And you need to be able to do this relatively quickly.

It's something that you just put on a standard article or there is some extra thoughts that needs to go into adding this extra 3D layer to their story.