
I build stuff at the edge (AI + Spatial Computing). Mostly just thinking out loud. Founder at @therealityuni
Manchester, England
Joined October 2018
- Tweets1.6K
- Following463
- Followers414
- Likes1.4K
Took me more than a year to build this but here it is: “Building AI infused Spatial Apps”
65 video lessons, beginner friendly and everything you need to build full blown 3D AI native spatial apps.
Link: realityuni.com/courses/visio…
1
4
553
Nikhil Jacob retweeted
Every startup should have a daily markdown file called "what_the_market_is_telling_us.md"
It updates every morning from the places where customer truth already lives:
1. Stripe for who pays, upgrades, downgrades, and churns
2. PostHog for what people actually do in the product
3. Intercom or Plain for support tickets/complaints
4. Granola or Gmeet transcriptions for sales calls/ customer interviews
5. HubSpot or Salesforce for CRM notes/lost deal reasons
6. Linear, Jira, or GitHub Issues for bugs and feature requests etc
7. Ideabrowser MCP for outside market signal: startup ideas, trend reports, social/search demand, AI research reports, and builder prompts that show what people are starting to want before it shows up in your own customer data.
Basically, the file should notice what changed in the business this week and not just be this summary of here’s what happened (which I think a lot of people have their agents do).
Why this is valuable:
1. Maybe new buyers are using different words than they were a month ago.
2. Maybe trial users are getting stuck in the same place.
3. Maybe upgraded customers all touched one feature right before they paid.
4. Maybe churned customers keep mentioning setup confusion.
5. Maybe sales calls are suddenly losing to a competitor you used to beat.
6. Maybe support tickets are revealing a workflow your product accidentally became responsible for.
You get the point.
The fastest way to PMF is understanding customers better than anyone else, and the highest signal customer insight is usually a change in behavior.
So I’d have the agent update the file every morning with the pattern it found, the receipts behind it, and the product or GTM decision it might affect.
For example:
“3 customers who churned this week all mentioned setup confusion, and 2 of them never invited a teammate.
This looks more like an activation problem than a pricing problem, so I’d look at team invite and onboarding before building another analytics feature.”
A little helpful tip for all those out there looking to get more from their LLMs.
I'm seeing the same pattern in spatial computing right now.
A creative director prototyping health tools on weekends.
An ex-engineer with ALS exploring accessibility features.
A software engineer building 100 visionOS apps — while working full-time.
The wave hasn't hit yet. But the builders are already here.
1
91
I won't ever shut it down completely.
I genuinely believe spatial computing is a high-potential bet.
I just don't know the timeline.
So: do my best, let God do the rest.
One foot in the present, one in the future.
1
63
Most visionOS learning roadmaps start in the wrong place.
Here's the order that actually works, at least the one that worked for me: 🧵
2
4
528
One thing nobody warned me about: what works on screen can feel awful on your face.
I had fast-moving bubbles in my app. Elegant in the simulator. Motion sickness-inducing on the headset.
The 2D screen cannot replicate the 3D experience. Build for the body, not the monitor.
1
313
The "Ready for Sale" email at the end of it all?
Worth every late night.
Not because the downloads will flood in; the platform is early and you know that going in.
Because you've shipped something real on a platform most developers are still too cautious to touch.
That's an asymmetric bet. Get in early.
1
1
231
I spent about $100 on 3D models for my visionOS app Inner Chronicles.
A mix of Sketchfab assets and quick Upwork freelance work.
You don't need to be a Pixar artist to ship a spatial app.
Play to your strengths and outsource the rest.
5
644
Two frameworks you need to know for visionOS:
ARKit: the brain. It reads the room: the floor, walls, hands, environment.
RealityKit: the front-end. It places your 3D content into that world.
ARKit tells you where the wall is. RealityKit lets you hang a virtual painting on it.
You don't need a Vision Pro to start building visionOS apps.
The simulator handles window-based apps surprisingly well.
Start there. Build your first floating UI. Get comfortable with the platform.
Buy the headset when you're ready to go 3D. Not before.
2
444
Getting that "Ready for Sale" email from Apple after submitting your first visionOS app is a feeling I can't fully describe.
It feels like planting a seed on a platform that doesn't fully exist yet.
You're not expecting a forest tomorrow. You're betting one will grow.
4
423
I thought my visionOS app was ready.
Then I tested it at the Apple developer lab in London.
The bubbles I had floating around the user? Beautiful in the simulator. A one-way ticket to motion sickness on the actual headset.
The simulator lies. The device doesn't. Test on real hardware before you ship.
3
385
visionOS isn't just iOS with a headset strapped on.
Think of it as iOS and 3D development having a baby.
Two worlds merged into one platform. New paradigm, familiar foundations.
That's what makes it learnable - if you know iOS, you're already halfway there.
3
324
Bill Gates was a side-hustler for 7 years before Microsoft.
School tinkerer. Traf-O-Data. Altair BASIC. Then, and only then, Microsoft in 1975.
The pattern is older than Silicon Valley.
1
3
499




