AIFoxAppAIFoxAppPortuguêsEspañolSign in

Product flow

From business context to an evolving app.

AIFoxApp keeps generation, manifests, builds, and updates separate and traceable.

1

Create your account and app

Create an account, accept the Terms of Use, and register the app with its name, package identifier, and platform. Authenticated access belongs to an organization.

2

Generate a preview

The public POST /preview/generate endpoint creates a preview session from a business name or website. It is IP rate-limited; sessions expire and may need to be generated again.

3

Version a manifest

Every build requires a manifest. Each new manifest receives a version, and its data must contain at least app_name and primary_color.

4

Start a build

Android enters the in-house Docker worker queue, which compiles an AAB in an ephemeral environment and uploads the artifact to the platform. iOS has a Mac-runner route and configurable fallback, but is not presented as ready without current runner and IPA proof.

What is already validated

The Android builder compiled the Expo/React Native chassis from a clean clone and produced a signed release AAB for the demo app. Its checksum, certificate, bundletool processing, and Google Play AVD installation were verified. Play Console, track, and publication remain separate validations.

Migrate an existing pipeline

Use POST /migration/importar_do_github to analyze a GitHub repository and create an initial configuration when it contains a recognized file: codemagic.yaml, eas.json, bitrise.yml, or appcenter-config.json.

OTA: gradual updates and rollback

Upload a ZIP bundle, promote it to a channel, and distribute it through production, staging, or another organization channel. A channel keeps the previous bundle as secondary; rollback swaps the current bundle with it. Rollout percentage is a channel field from 0 to 100.

Assisted publishing

Content under review. Internal Terms clause 4 describes a prior review and no-extra-cost resubmission for eligible correctable issues in the same request, with exclusions for customer content and false, incomplete, or unavailable information. It is not a refund promise and does not control store-review timing.

Push notifications

The API sends notifications through FCM to registered devices, with an Android and iOS flow. The sending infrastructure is integrated; end-to-end delivery confirmation on a physical device is still pending. Native Analytics requires Firebase/Analytics configuration per package and is not available yet.

App modules

The visual editor organizes catalog, booking, forms, loyalty, accounts, content, commerce, and intelligence capabilities. Segment suggestions are additive, and publishing creates a new manifest version without deleting existing settings.

Content and operations

Gallery, map, catalog, booking, menu, events, documents, audio, video, and RSS.

Relationships

Push, loyalty, coupons, referrals, members, profile, chat, and community.

Commerce and intelligence

Cart, search, tracking, integrations, grounded assistant, assisted autofill, and Atomic Security.

October 2026 updates

The 2026-10-15 release shipped with every item proven by automated tests (real PostgreSQL, a browser or an Android emulator). Anything not yet proven is not listed here.

App content (articles, about, contact, agenda)

Proven: Tests on real PostgreSQL and a browser; protected media served only to members with access. Limit: Protected media only in apps with their own domain; audio and video streaming not yet.

Bookmarks and RSS article feed

Proven: Feed sync, reading in the web app and in the emulated Android app. Limit: Podcast via RSS under review.

Community and chat

Proven: Member and support conversations, block and unblock, isolation between apps. Limit: none recorded.

Booking with seats

Proven: Race for the last seat resolved with no double booking. Limit: none recorded.

Stock and in-store pickup

Proven: Stock matches orders with 16 concurrent clients, 0 conflicts. Limit: Online payment still being prepared.

Owner portability

Proven: Encrypted export for the owner only, import with a tested round trip. Limit: none recorded.

Signed webhooks

Proven: 11 of 11 tests with signature verification. Limit: Ready-made third-party connectors not yet.

API

Proven: Isolation between organizations; keys scoped per app with an expiry date. Limit: none recorded.

Account deletion by the user

Proven: In the web app and on Android; the old login stops working. Limit: none recorded.

Content-preparation AI and analytics

Proven: Ready and off by default, with consent, preview and rollback. Limit: Activation depends on the owner.

JSON bodies require Content-Type: application/json; without it the API answers 422, on purpose.

Grounded assistant

The assistant uses only the app's published context. Operational audit records keep hashes and source references, not raw questions or answers.

Atomic Security

The audit can be refreshed from the editor and remains a separate gate from building, signing, and store publication.