Anything

What Anything builds

Anything, previously known as Create, is an AI app builder for web and mobile projects. You describe the application, then refine its screens and behavior through a conversation with a coding agent. Its first-app guide covers user interfaces, databases, sign-in, backend functions, integrations and payments. This makes it relevant to founders exploring a product, service businesses building customer tools, and developers who want an editable starting point.

The useful distinction is between generating an interface and assembling an application that stores data and serves users. Anything supports both kinds of work, but the requirements still come from you. A booking screen needs rules for availability, cancellations and staff access; a convincing visual preview does not establish that those rules work.

Web projects and native mobile screens

The builder supports iterative changes to the app's design and functionality. You can ask for another screen, adjust navigation, add a database-backed view or connect a backend action. Its mobile documentation describes Expo and React Native projects, with device capabilities such as camera input, location and audio. Web and mobile versions can connect to the same Anything database.

Mobile previews have an important boundary: the browser cannot reproduce every phone capability. Anything documents connecting Expo Go to preview on a physical device. A camera upload flow, for example, should be checked on the intended phone rather than accepted because a placeholder button appears in the browser. Mobile store submission also has separate account and review requirements.

Example: a repair appointment app

Start by specifying a small web application where customers choose a repair service, request a time and see their own appointments. Ask for the screen layout first, then add the appointment records and customer sign-in. Define which fields customers can change and which actions belong to staff. Use sample bookings to check conflicting times, missing contact details and a cancellation.

Next, request a mobile version if customers need phone-specific functions, such as attaching a photo of the damaged item. Preview that flow on a device. Before publishing, inspect the pages, backend functions and database changes included in the release. The publishing guide distinguishes a private preview from a public web URL and explains publishing the backend alongside mobile projects.

Access, credits and launch limitations

Anything's current subscription documentation says building an app requires a paid plan. Pro and Max differ in capabilities; check the current plan information before choosing one. The credit guide explains that building messages and AI integrations running in published apps can both consume credits. Usage therefore continues beyond the initial prototype when an app uses metered AI features.

Publishing a mobile build is not automatic approval by a store. Anything's App Store guide requires an active Apple developer account, app information, privacy disclosures and review through Apple's process. Generated code and automated checks also need your own functional and access-control review. For a customer-facing application, budget for maintenance and test the actual user journey before inviting real customers.