Your app questions,
answered.

Div-idy is an AI software builder for personalized websites, apps, tools, and browser games. Describe what you need, from a calculator or directory to an AI assistant, then make it your own with follow-up prompts.

Div-idy can build interactive websites, calculators, quizzes, forms, blogs, catalogs, location directories, AI assistants, and lightweight browser games. Combine React interfaces with supported data, AI, Maps, and multiplayer features. Describe a specific audience and task so the builder can choose the relevant capabilities.

No. Describe your idea in everyday language and ask for changes in the prompt bar. Div-idy generates the code; you try the result and check that it works the way you want before sharing it.

To start a Div-idy app, sign in, create a project in My Projects, and describe what users should be able to do. Include the pages, data needs, and visual direction. Wait for the saved draft, test the main action, request any changes, and publish the pages you want to share.

Your first month on the Basic plan is free. After the trial, the plan renews at the price shown at checkout unless you cancel. Creating and editing projects uses build tokens; running AI features uses a separate allowance.

See current prices and trial terms

Div-idy build time depends on the request, source size, and model work. A larger app can take substantially longer than a small edit. Follow the build status and wait for the saved result before testing. Progress messages or partial output do not mean the app has finished.

An accepted Div-idy build can continue on the running server after you leave the page. Return to the project to check its status and saved result. Recovery does not automatically start another paid generation, and a server interruption can still prevent the build from completing.

Check the Div-idy project’s saved result, build status, and error message before resubmitting a failed request. Keep the original prompt and avoid duplicate requests while a build is active. For support, include the project, page, approximate time, and observed problem without credentials or private customer records.

Yes. Ask for an AI assistant, a form that saves submissions, or a map with searchable locations. Div-idy provides built-in tools for these features, with usage limits based on your plan.

Div-idy generates React components written in TypeScript and TSX, alongside styles and supporting source files. It checks and compiles the source into HTML, CSS, and JavaScript for the browser. The result supports interactive app behavior, while you can continue editing through plain-language prompts.

Div-idy supports a Home page and additional child pages, each with its own content and metadata. Describe the pages and navigation you need in your prompt. You can edit a selected page, use consistent data across pages, and choose which pages to publish.

Div-idy can customize fields, calculations, filters, steps, content, and interactions as well as visual design. Describe what should happen after each action and where data should be saved. For later changes, identify both the behavior to change and the parts to preserve.

Yes. Open your project and describe the change. Edits are saved as a private draft, so your live page stays unchanged until you publish the update.

Div-idy can generate responsive React layouts, touch-friendly controls, readable forms, and mobile navigation. Include those requirements in your prompt and test the app on narrow screens. Where app distribution is enabled, Publishing also offers a separate app link for Home Screen installation.

Div-idy supports its prepared React and TypeScript runtime, local source modules, and built-in services for data, AI, maps, and multiplayer. Arbitrary npm packages and custom server code are outside that runtime. Describe the feature you need so the builder can use supported capabilities.

Div-idy supports lightweight room-code games with a host, participating players, and shared game state. It suits quizzes and small shared browser games. Test through a published project using separate player sessions; the feature is not a large-scale competitive or anti-cheat game backend.

You can attach supported photos and screenshots to Div-idy prompts using the image control, drag and drop, or paste. Explain whether each image should appear in the app or guide its design. Check the attachment thumbnail before sending, then review cropping, layout, and alternative text.

Div-idy can create informational websites and interactive React web apps. A portfolio or landing page mainly presents content; a calculator, searchable directory, or quiz also responds to user input. Explain whether visitors should read, calculate, filter, submit, or use an AI feature when you write the prompt.

Div-idy can build React calculators for estimates, conversions, scoring, and other defined formulas. Specify the inputs, units, formula, rounding, and example results. Ordinary calculations do not need an AI call. Test boundary values and incorrect inputs before sharing the calculator.

Div-idy checks and compiles generated React and TypeScript code before saving a successful build. Those code checks do not establish that every interaction, integration, calculation, or layout works as intended. Review the saved preview, try error and empty states, and test the published experience before relying on it.

Div-idy’s built-in database supports visitor form submissions, private owner-managed records, and explicitly published content that visitors can read. Apps can also store information locally in a browser. Choose the data option based on who should read or edit the information and whether it needs to be shared.

Div-idy can build a React blog, news page, or article library with owner-managed content. The owner creates and edits records in the private preview, then explicitly publishes them for visitors. Saving a content draft keeps the previously published version unchanged until the next Publish action.

Visitors can submit supported forms on a published Div-idy app without creating a Div-idy owner account. Ask for input validation, a loading state, and confirmation after saving succeeds. Submitting a form does not give a visitor permission to read other submissions or manage private records.

Div-idy database views control how the owner sees existing records through tables, cards, galleries, filters, and labels. Changing a view does not publish records or grant visitor access. Manage record visibility separately from display preferences.

The generated-app runtime currently provides no visitor sign-up, sign-in, or per-user authorization API. A generated login screen alone does not create secure accounts. Div-idy owner accounts, private owner records, public content feeds, and game-room identities have separate, specific permissions.

Device-local storage in a Div-idy app belongs to that browser and does not automatically sync. Clearing browser data can remove it. Use the built-in database for supported shared submissions or owner-managed content, and specify which information visitors should be allowed to read.

Div-idy can combine a searchable React directory, owner-managed location records, and Google Maps. Ask for filters, addresses, map markers, and a useful list view. Publish the location records visitors should see and verify real coordinates and map behavior on the addresses you will share.

Div-idy’s Database tool exports the current filtered and sorted view as CSV using its displayed fields. Advanced options copy a selected collection as JSON or download the loaded project database as JSON. Refresh before exporting. JSON exports do not use view filters; these are data exports, not a standalone app backup.

Div-idy apps support AI text generation, image understanding, image generation, and text-to-speech. Examples include writing assistants, picture explainers, image generators, and read-aloud tools. Each request should start from an intentional user action and uses the owner’s AI-tool allowance separately from building the app.

Div-idy supplies the connection for its built-in AI features, so you do not need to paste a provider API key into your generated app. The platform applies authentication and usage limits. Keep secrets out of prompts, browser source, and public content.

Div-idy can build an AI image generator with a prompt field, an explicit Generate action, and a display for the returned image. Include loading and error states and account for AI-tool usage. This feature creates images during app use; attaching a photo to a build prompt supplies an existing image.

Div-idy’s image-understanding feature returns text about a supplied image, and its text-to-speech feature returns playable audio. Both are supported user-triggered AI actions. The generated-app interface does not currently expose speech transcription, realtime voice conversations, image editing, or video generation.

Div-idy AI Context supplies reference information and response instructions to an app’s text and image-understanding features. Use it for relevant business facts, policies, or examples. Context does not train a new model or automatically connect a private knowledge system, and answers still need review.

Div-idy’s Google Maps integration supports location lists, map markers, place search, and directions where the underlying service is available. Ask for a usable address or list fallback alongside the map. Test actual locations and routes, including any connected custom domain.

A Div-idy project icon identifies the project in My Projects and is managed from the project menu. Publishing’s installable-app settings have a separate app icon where that feature is available. Changing either icon does not replace images inside the generated React pages.

A successful Div-idy build saves a private draft. Visitors keep receiving the published version until you publish the updated page. Owner-managed content records also have distinct Save and Publish actions, so a saved post draft does not automatically replace its public version.

Your draft stays private. When you are ready, choose which pages to publish and leave the rest private. Published pages are unlisted, but anyone with their link can view them. Unlisted does not mean password-protected.

Anyone with an unlisted Div-idy link can open the published page. Unlisted sharing is not password protection or visitor authentication. The editor can remain private while the published link is accessible, and private records should stay out of publicly readable content feeds.

Div-idy reviews the saved content intended to go live during publishing checks. A reported content issue or an incomplete check can prevent sharing. Read the specific message, correct the draft if needed, and retry the check. A successful build is separate from approval to publish.

You can embed a published Div-idy page in a website that allows iframe embeds. In Publishing, choose a live page under Embed on a website, set the frame title and height, and copy the code. The embed displays the published page rather than private draft changes.

Yes. Share a published page by link or embed it on a website that supports embeds. Where domain connections are enabled, you can connect a www address or another subdomain, such as app.yoursite.com.

When domain connections are enabled in Div-idy Publishing, you can connect a www address or another subdomain using the displayed verification and routing records. Wait for connection and HTTPS confirmation. The current setup requires a visible CNAME record and does not support bare-domain connections.

Where app distribution is enabled, Div-idy Publishing provides an app link with a name, icon, and theme color. Visitors choose installation through a supported browser. The installed web app needs an internet connection; installation is not automatic and does not submit the app to a native app store.

Where notifications are enabled, Div-idy app visitors can choose to subscribe and grant browser permission. The owner can review and send an update that opens an already-live page. Delivery depends on browser and device conditions; an accepted send does not confirm that every subscriber saw the message.

Deleting a Div-idy project does not remove AI usage already incurred during the account’s billing cycle. It removes the project rather than undoing completed AI work. Check account usage and renewal information for the current allowance.

AI summaries and questions in Div-idy Analytics use the AI-tool allowance. They can help interpret a specific question about available metrics. The summary explains the reported data; it does not independently prove visitor intent or guarantee that a proposed change will improve results.

Div-idy gives eligible browsers a stable assignment between two test versions with a 50/50 allocation rule. Actual small samples can be uneven, and refreshing does not necessarily change the version. Review the measured goal and sample size before treating a difference as evidence of improvement.

Div-idy unique-visitor counts estimate browser activity, not verified individual people. One person can use several browsers or devices, and multiple people can share a browser. Storage changes and blocking also affect measurement. Interpret visitor counts alongside visits, sessions, and supported events.

Div-idy build tokens cover app generation, prompt edits, publishing safety checks, and generated project icons. AI-tool usage covers supported AI actions inside apps and AI-assisted tools such as analytics summaries. An app with no visitor-facing AI can still use build tokens when you create or edit it.

Div-idy supports A/B tests on eligible published pages. Create a test, edit its separate variant, review both versions, and complete approval before making the test live. Eligible browsers receive stable assignments. Use measured events and sufficient traffic to assess the change; the tool does not automatically prove a winner.

Div-idy’s hosted customer pages currently request no indexing and are excluded from the marketing sitemap, including connected-domain delivery. Publishing and metadata do not override that policy. Div-idy’s public product documentation and FAQ are separate pages written for discovery and included in the public sitemap.