[dthedavid]

Nice project. I’m building a similar project. It’s open source too.

https://github.com/DonkeyUseCorp/Donkey

It’s mostly a web app with a native swift companion app to access local resources like TTS, file storage and video rendering.

I arrived at the same conclusion as you; every app should have AI chat. Just give it full access to the app like a real user. I found that users prefer talking to the AI when editing vs clicking around.

[scoot]

> Donkey Vision — a screen-understanding API that turns any screenshot into structured, clickable UI, so you can build computer-use tools of your own.

Not faulting your (necessary given today's reality) work, but sad to think that the Amiga still remains ahead of it's time some 36 years later (since ARexx was bundle with the OS), or closer to 40 years if you count when v1 was released separately.

ARexx allowed any application that supported it (and most productivity apps worth their salt did) to communicate with each other, and to be scripted - essentially a standardised API for applications.

We're slowly getting there (at least for SaaS apps) with MCP, but screen scraping shouldn't ever have been necessary.

[scoot]

Donkey is slick. Love the minimal UI.

Edit: Having played with both a bit, and with no disrespect to OP, yours is a significantly better product.

[harrisontin]

no disrespect taken :) What's something that we can do better?

[scoot]

Ifound Palmiers interface dense, cluttered, and confusing - just take the panel top left (to the right of chat) for example. So much going on in one small space.

Donkey Cut offers more functionality in less space, and everything is easy to find and understand. It isn't without bugs, but the structure is there for it to be great