Kate Steinmeyer

[Kate Steinmeyer @kateelspeth]

@nevryk_s @OpenAIDevs @thsottiaux same

[Kate Steinmeyer @kateelspeth]

When Codex goes down 😢

[Kate Steinmeyer @kateelspeth]

I just submitted my interactive ai demo app to the app store!

This has always been a dream of mine and I can't believe it's happening right 👏 now 👏.

This is your sign to go build. You don't need to be an engineer. This is the best time ever to start building!

check out my app @maybeundoapp

[Kate Steinmeyer @kateelspeth]

Who else is using Codex instead of Xcode to build their iOS apps?

Even with GPT inside Xcode I still just use Codex.

Kinda wild how complicated Xcode is.

It doesn't need to be and thanks to Codex @OpenAI

#xcode #codex #aitools

[Kate Steinmeyer @kateelspeth]

soooo I’ve had this account since 2009…
it’s never gone mild viral. kinda crazy. do i need to create a new account?

[Kate Steinmeyer @kateelspeth]

What if Your Presentation Could Build itself While You Talk?
https://t.co/GF0cX4gtNs

#interactiveaidemo #aidemo #aipresentation

[Kate Steinmeyer @kateelspeth]

If you want to try AI slides that takes the content to the next level, try @maybeundoapp

https://t.co/DN9zVAiwSA

[MaybeUndo @maybeundoapp]

Claude + MCP for MaybeUndo platform - Interactive Al Demos and Al Video Creation
#aitools #aieditor #aivideogeneration #aipresentation #interactiveaidemos

[Kate Steinmeyer @kateelspeth]

MCP is not just a technical integration.

It is a product boundary design problem.

If you’re building an MCP server for your app, the question is not only:

“Can an AI assistant use our product?”

It is:

“What should the assistant see, what should it do, and where does the permission boundary end?”

The safest pattern is usually:

Expose product data and workflow logic.
Do not expose your whole product.
Keep tools narrow.
Make scopes clear.
Prefer read access before write access.
Audit meaningful actions.

If a user connects your app to an AI assistant and authorizes access, that is not secret exfiltration. That is the workflow.

The responsibility is making sure the user understands what they shared, why it is needed, and what the assistant cannot access.

That is where trust gets designed.

https://t.co/wSkGxwiZDC

#mcp #founder #productdesign #uxdesign #ai

[Kate Steinmeyer @kateelspeth]

We’re still building demos, decks, and videos like they’re separate things.

They’re not.

They’re all the same story — just rewritten over and over again.

That’s the problem I’m working on:

https://t.co/tloJ4Ki48m

[Kate Steinmeyer @kateelspeth]

2025
143k lines of code
Built slowly.
Built deliberately.

This is the foundation.

Progress doesn’t look linear
until zoomed out.

[Kate Steinmeyer @kateelspeth]

2025 ❤️ the end of design software
2026 🩶 the year of Sensemaking

[Kate Steinmeyer @kateelspeth]

Build the agents and the agents will build the business.

[Kate Steinmeyer @kateelspeth]

one day your ai assistant will be able to follow you everywhere, watch you walk down the street.

as you arrive to the train station platform,

your ai assistant will say ~

you made it, just in time!

[Kate Steinmeyer @kateelspeth]

The world noticed, the moment ignored.

[Kate Steinmeyer @kateelspeth]

A passing moment, folded into years.

[Kate Steinmeyer @kateelspeth]

@julianweisser https://t.co/aX3xivnxvP

[Kate Steinmeyer @kateelspeth]

Time doesn’t answer every question.

[Kate Steinmeyer @kateelspeth]

at Techcrunch Disrupt! Let’s connect!