Natively.dev is now Newly: current product guide

In short

Natively became Newly. This service creates cross-platform mobile projects with AI, but the buyer still owns review, testing, store accounts, compliance, data decisions, and ongoing operations.

• Use newly.app and docs.newly.app for the current product. Treat older Natively screenshots, plan names, and feature lists as historical until verified.
• The generated stack currently uses React Native and Expo, with Supabase promoted for database, authentication, storage, and real-time features.
• Newly's FAQ currently says there is no free plan and lists a starting price of 25 US dollars per month with 50 credits.
• The product advertises GitHub or ZIP export and ownership of generated code. Test an export in a clean environment before relying on portability.
• AI output can contain errors, security issues, third-party rights, and non-unique material, according to Newly's terms. Independent review remains the user's duty.
• Run the hardest real workflow on iOS and Android, then verify backend policies, builds, signing, store submission, monitoring, and recovery.

What happened to Natively.dev?

The natively.dev domain currently opens Newly. Newly's About page uses the phrase formerly Natively and identifies a Stockholm-based team. That first-party statement and the live redirect are stronger identity evidence than an old directory listing or review page.

A similarly named product at buildnatively.com converts existing websites into mobile apps. It has different documentation, plans, and technology. Do not mix its pricing or features into an evaluation of Newly.

Confirm the Natively-to-Newly change on the current company page.

How does Newly build an app?

Newly starts from a natural-language description. Its documentation says the service generates a React Native and Expo project that can be previewed and refined through conversation. Marketing pages also describe visual editing, Supabase services, source export, and mobile-store deployment.

1. 1Describe the audience, problem, core screens, data, roles, device features, and success condition.
2. 2Review the generated information architecture and first user path before adding more features.
3. 3Connect or inspect the Supabase database, authentication, storage, policies, and environment configuration.
4. 4Preview on representative iOS and Android devices. Test loading, empty, error, permission, offline, and recovery states.
5. 5Export to a repository or ZIP and run the project with documented dependencies outside the hosted workspace.
6. 6Build signed store artifacts, prepare listings and policies, submit through organization-owned accounts, and resolve review feedback.

Use the current Newly documentation for setup, iteration, and deployment steps.

Is the output native?

Newly says it generates React Native and Expo code rather than a webview wrapper. This is a cross-platform native framework approach, not two independent Swift and Kotlin codebases. The result can render native components and build iOS and Android binaries. App quality still depends on the generated implementation, dependencies, device behavior, and testing.

• Inspect navigation, gestures, text input, keyboards, safe areas, status bars, permissions, deep links, and orientation.
• Test camera, location, notifications, biometrics, purchases, background work, files, and offline behavior when required.
• Measure startup, screen transitions, large lists, images, animation, memory, network use, and older-device behavior.
• Check platform conventions separately. Shared code does not remove every iOS and Android difference.

How much does Newly cost?

Newly's current FAQ says the service has no free plan. It lists a starting price of 25 US dollars per month, including 50 credits and core build, preview, export, APK, AAB, and simulator features. The pricing page is dynamic, so confirm the final currency, tax, renewal, included usage, top-ups, and plan entitlements at checkout.

Check Newly's current FAQ and pricing page before subscribing.

The May 2026 terms say paid plans renew automatically unless cancelled before renewal. Allocations reset according to the plan unless rollover is stated. Top-up credits are final, expire after twelve months, and require an active paid subscription. Refund eligibility is narrow, including a two-day first-subscription condition with low credit use. Read the complete terms.

• Apple and Google developer accounts, organization verification, taxes, store commissions, and payment processing.
• Supabase or another backend, storage, bandwidth, email, SMS, maps, AI APIs, analytics, monitoring, and logs.
• Domain, support, design, content, accessibility, security review, legal review, testing devices, and incident response.
• Engineering time for generated-code review, dependency fixes, native modules, build failures, store rejections, and migration.

Do you own the generated code?

Newly's terms say that, as between the customer and Newly, the customer owns Customer Data and AI Output. The ownership clause remains subject to third-party rights in models, training data, outputs, packages, fonts, media, and other dependencies. The platform and Newly Materials remain owned by Newly and its licensors.

Marketing pages promise GitHub or ZIP export. Prove the handoff before depending on it. Export a small project, install dependencies, configure environment variables, run tests, build both platforms, connect a test backend, and document any Newly-only service. Code access is valuable, but an untested archive is not an exit plan.

Read Newly's current ownership, AI-output, billing, and service-dependency terms.

What happens to prompts and project data?

Inputs and related data can be transmitted to infrastructure and AI providers, including Anthropic, OpenAI, or Google, according to Newly's terms. The Customer Data clause grants Newly a broad business-purpose license outside identifiable personal information. It describes an opt-out by contact or an eligible enhanced-control plan. Obtain qualified review for your organization.

The terms prohibit submitting protected health information and special data such as financial account numbers, government identifiers, or biometric data. Use synthetic data in the prototype. A product that will later process sensitive information needs a separately approved architecture, contracts, controls, and compliance review.

Review Newly's privacy policy together with the more detailed Customer Data terms.

Treat production-ready as a testable claim

Newly markets production-ready output. Its terms also state that AI output may contain errors, inaccuracies, security issues, or other defects. They require independent review and testing and do not guarantee uniqueness, third-party-rights clearance, accuracy, or fitness. Use production-ready as a set of acceptance criteria, not as an automatic status.

Correctness

core workflows pass with representative accounts, data, permissions, failure modes, and concurrency.

Security

authentication, authorization, secrets, row policies, dependencies, inputs, uploads, payments, and abuse controls are reviewed.

Accessibility

keyboard and switch use, screen readers, focus, text scaling, contrast, motion, labels, errors, and touch targets are tested.

Privacy

collection is minimized, documented, consented, retained, deleted, exported, and handled under approved agreements.

Reliability

monitoring, logs, alerts, backups, restores, rollback, incident response, service limits, and ownership are documented.

Release

both signed builds install, store metadata is accurate, policies are complete, and reviewers can access required functions.

Does one-click deployment guarantee approval?

No builder can replace the store's review decision. Newly can automate build and submission steps, but the developer remains responsible for the application, account, content, disclosures, privacy, payments, rights, and policy compliance. Keep signing keys and store accounts under the correct organization.

Review Apple's current App Review Guidelines before designing the release workflow.

Review the current Google Play policy center before preparing the Android release.

Run a paid evaluation with an exit test

1. 1Set a fixed credit and time budget. Choose one workflow with real complexity but no sensitive data.
2. 2Create roles, representative records, validation, loading, empty, error, offline, and account-deletion states.
3. 3Connect one approved external service and inspect how keys, failures, limits, and logs are handled.
4. 4Test the app on at least one representative iOS device and one representative Android device.
5. 5Export the complete project and reproduce local setup, tests, backend connection, and signed builds outside Newly.
6. 6Calculate twelve-month cost at expected usage, including credits, services, stores, people, support, and incidents.
7. 7Proceed only when the evidence meets the written acceptance criteria and a named team can operate the result.

Use Better Design's AI guardrails when reviewing the generated product and interface.

Frequently asked questions