What AdenAI can and cannot do

Better to know this beforehand than after your third ticket. This article says what AdenAI is built for and what it is not built for.

What gets built here

Websites and applications that run in a browser. From a one-page presence for a joiner's workshop, through a site with sign-in and a protected area, all the way to an online shop.

What AdenAI builds works on a phone too. But these are not native apps: nothing you download from the App Store or Google Play and install on an iPhone or an Android phone. What you get is a page that opens in the phone's browser and is used there like an app. For the vast majority of plans that is exactly right, and for the rest AdenAI is the wrong tool today.

The code is yours. Always, even if you leave again. See Where your code lives.

What works reliably

• Creating, rebuilding and rearranging pages. New subpages, moving sections around, changing the navigation.
• Text. Writing it, shortening it, changing the tone, putting it into another language.
• Looks. Colours, spacing, type sizes, light and dark, mood.
• Forms. Contact, newsletter sign-up, multi-step input.
• Sign-in and protected areas. Registration, login, forgotten password.
• Online shop. Products, basket, payment through Stripe, orders, discount codes. See Online shop.
• Being found. Page titles, preview text for search engines and social networks, sitemap.
• Finding and fixing faults. Describe what you see and what you expected instead.

What AdenAI cannot do

The honest list. None of these is a bug you need to report.

Rebuild somebody else's site. You can put example sites in as images, and AdenAI takes the effect from them: the colour world, the calm or the loudness, how generous the spacing is. Layout, text, logos and image composition it explicitly does not take over. There are two reasons and both count: a copied site is a legal problem, and a copy is never good. Someone who knows your reference should say "same handwriting", not "same site".

Invent content only you have. Your prices, your opening hours, your references, your photos. Whatever you do not write into the ticket or upload becomes a placeholder, and placeholders look real. So check every number on the finished page.

Take responsibility for your legal texts. An imprint and a privacy policy are created along the way, but with sample data. They are a scaffold, not legal advice. Before your site goes public, your real details belong in there, and if in doubt somebody who knows the field should look over them.

Reach into your other accounts. AdenAI has no access to your mailbox, your inventory system or your social media account. If your site is to talk to an outside service, you store that service's credentials in the project settings under Zugangsdaten (Credentials). They are stored encrypted, and AdenAI only ever learns their names, never their values.

Fetch something that sits out on the web. Fonts, icon sets or images from third party services are not loaded in. That is deliberate: otherwise every visit to your site reports the visitor's IP address to a third party, and if that service goes down, your site is broken. You can upload a font file you bought, and then it lives in your project.

Guess what you mean. On something genuinely decisive AdenAI asks. On everything else it decides for itself, and then it is its decision, not yours. That is the most common reason for a result that does not fit. See Describing what you have in mind.

What only you can take care of

Some things nobody can take off your hands, because they hang on your name:

• A Stripe account, if you want to take money. What that involves is under Online shop.
• Your domain. You set the records at your provider yourself, and we tell you exactly which. See Connecting your own domain.
• Your content. Text, images, prices. And the rights to the images.
• The decision about what goes live. Nothing becomes public by itself, see Your draft and the published version.

How AdenAI works, in one paragraph

A ticket is checked first: if something decisive is missing, you get a question back. Then the brief is broken into steps, built step by step, and at the end your site runs as a draft. Per account AdenAI only ever works on one ticket at a time, so that two runs do not get in each other's way. Further tickets wait in line and start on their own.

What that costs in time and credits is under Credits and under How big should a ticket be?.

What is not yet smooth today

We are before launch, and a few things are built but not switched on yet. Each one is noted in the article it belongs to, and here is the list to look up:

• Emails do not reach external addresses. You see notifications in the dashboard.
• Not every purchase is unlocked yet. Plans, extra credits, projects, pages and team seats are all built as purchases and all run through Stripe. Whether one of them is ready in your account is told to you at the place where you make it: either there is a buy button with the price, or the mark Bald verfügbar (Coming soon) and a sentence about it. In the second case you write to support and we unlock it by hand. The prices apply either way. See Inviting your team and roles and What happens after the trial?.
• If you run out of credits during the trial, write to us in support and we will top you up.

If you find something that is not listed here and still does not work, tell us. That is exactly the feedback that moves us forward.