Straight answers about building apps with AI.

limewAI is an AI app builder. You describe an app in plain language, or add an image for context, and limewAI creates a working web app with source code and a live preview.

Create a project and describe the result you want, the people who will use it, and the main tasks it should support. limewAI handles the planning, source generation, build checks, and preview, while you guide the result through conversation.

State the kind of app, who it is for, and the most important action it must complete. Useful details include the pages, fields, calculations, records, visual tone, and whether people need to sign in.

limewAI is for business owners, teams, specialists, creators, and people exploring a software idea. It is most useful when you understand the problem and desired outcome but do not want to begin with a full technical specification.

You can write requests in English, Arabic, or a mixture of languages. limewAI processes the request for building while the generated app language and right-to-left direction follow the project’s language choice.

limewAI can build public websites, calculators, dashboards, stores, booking interfaces, portals, trackers, record-management apps, and other browser-based software. A focused first request usually produces a clearer first version than a request for an entire large platform at once.

limewAI generates ordinary web-app source and runs build and browser checks before showing the result. The preview is intended to be an interactive app, not a static design mockup.

Time depends on the size of the request, AI response time, validation, packaging, and preview startup. A focused app can be ready in minutes, while a larger app or a request needing repair can take longer.

Yes. Requests that create, edit, list, or search records can include persistent data and API routes. You should test the generated permissions and data rules before using the app with sensitive or regulated information.

limewAI currently builds responsive web apps that work across desktop and mobile browser widths. A phone screenshot can guide a mobile-first layout, but the generated result is a web app rather than a native iOS or Android package.

Yes. Attach the image with a sentence explaining whether you want to follow its layout, borrow its style, reproduce a function, use it as content, extract information, or fix a problem it shows.

limewAI can use a screenshot to follow layout, proportions, colours, spacing, and interaction ideas. It does not intentionally copy another company’s logo, brand name, or trademarked text into your app.

Yes. Tell limewAI that the image is content and where it should appear, such as a logo in the header or a photo in a product card. Uploaded images are stored with the project and prepared for web use.

Yes. Ask it to extract the visible content and use it in the app. Review the result carefully because small text, glare, handwriting, or a low-quality image can affect extraction accuracy.

The build continues from your written request instead of stopping. limewAI keeps the message and gives a plain notice that the image could not be used.

Yes. Send a follow-up message in the project chat describing the change. A successful edit creates a new version of the same app so earlier work remains part of the project history.

Name the page or area, say what should change, and state what should remain the same. For example, “On the checkout page, make the main button green and keep the layout and wording unchanged” is easier to verify than “improve it.”

An edit is intended to improve the existing version in place. limewAI compares the result with the previous app and keeps the previous working version when a change cannot be completed safely.

Yes. The project version history lets you select an earlier version and make it current. Later edits then continue from the version you chose.

Yes. Attach a screenshot and describe the problem, such as overlapping elements or an unreadable button. limewAI uses the screenshot to locate the affected area and focuses the edit there.

The live preview is the running version of your generated web app inside the builder. It lets you use the app’s controls and review a version before publishing it.

Interactive preview machines can stop when they are not being used. limewAI can show the last saved view immediately while it starts the interactive app, then switch to the running preview when it is ready.

Yes. The Publish area can create a public link for a completed version. The current plan and platform publication limits determine how many projects you can keep published.

A sleeping published app starts again when it is visited. While it starts, visitors may briefly see a simple starting message instead of a connection that appears to hang.

A Free-plan publication is eligible for removal after 30 days without recorded activity. A visit records activity and paid publications do not use that Free inactivity limit.

Credits represent AI and build usage inside limewAI. The product shows available, reserved, and used credits, and records wallet changes in a credit ledger.

limewAI is designed to keep or create a working preview even when a step cannot finish. When a job does not deliver a usable result under the refund rules, its reserved or charged credits are released or refunded.

Yes, when credit packs are active on the Billing page. A verified payment adds the pack’s credits to your wallet without requiring a plan change.

limewAI uses renewal invoices and payment links rather than an automatic recurring charge. A verified renewal payment extends the plan and adds the credits for the new period.

An upgrade takes effect after payment is verified. A downgrade is scheduled for the end of the paid period, and cancellation keeps the current plan active until that period ends before moving the account to Free.

As between you and limewAI, you own your generated application source and content. Third-party packages, open-source software, and material you did not own remain subject to their own rights and licences.

limewAI uses HTTPS, hashed passwords, signed sessions, project ownership checks, encrypted cloud storage, managed secrets, and generated-code safety checks. No online service can promise absolute security, so review the Security page for the controls confirmed in the current platform.

Customer project routes check both the project identifier and the signed-in owner. Preview access is also tied to one user and one preview session rather than granting general account access.

The AI provider can receive your request, relevant project context, selected source files, validation errors, and attached images when image understanding is enabled. limewAI sends what is needed for the operation rather than your complete account record.

No card fields are collected in the limewAI application. Hosted checkout is handled by PAY2M, while limewAI stores the order, amount, status, callback history, and provider transaction reference needed for billing records.

Keep the project open while limewAI starts the interactive preview. The saved version should remain visible, and you can use Try again if startup reaches its limit.

The requested update did not pass the checks needed to replace the working app. limewAI keeps the previous version so an unsuccessful edit does not remove or break what you already had.

A broad request may be delivered as a smaller working version when the complete result cannot be produced safely in one pass. Review what is present, then ask for the most important missing page or behaviour as a focused edit.

A payment must be verified against its limewAI order before credits or a plan are applied. PAY2M callbacks can be delayed, so the Billing page may show that confirmation is still in progress.

Start with one clear outcome, identify the main user, and describe the action that must work. For edits, name the page and element, explain the desired change, and say what should stay unchanged.