What your app can do

One row per platform capability. This is the same register every part of Hamish answers from, so it cannot disagree with the product.

In a published app

Your app can store and read data, and it keeps working after you publish.

Your app can have its own sign up and sign in for your visitors, and it keeps working after you publish.

The app can call Hamish LLM to understand and write text for its visitors, and it keeps working after publishing.

Apps built with Hamish can generate images for their visitors. The app's owner controls and pays for this.

Hamish can generate images for the app at build time.

With your own key

Your app can call an outside service once you add that service's own key on the APIs page. Hamish does not supply the key.

In the Studio preview only

While you build, Hamish can stand in for an outside service with realistic sample data so you can see the shape of your app. That stand in does not travel to your published app.

Hamish can show a checkout flow while you build so you can see how it feels, but it does not take real payments in a published app yet.

Live updating between visitors works while you build, and it is not in a published app yet.

Sending email from your app works while you build, and it is not in a published app yet. Capture the enquiry as data instead, which does keep working.

Letting visitors upload files works while you build, and it is not in a published app yet.

In app notifications work while you build, and they are not in a published app yet.

Search across your app's records works while you build, and it is not in a published app yet.

Using Hamish on a phone

You can plan your app on your phone and start the first build there. Hamish builds it while you watch.

You can change your app and publish it from your phone.