Skip to content

Newly

Newly, formerly Natively, builds iOS and Android apps from a description and lets you preview native builds in cloud simulators.

Visit Newly

Why check the native preview before sharing a phone app?

Newly generates a React Native app, a code project for building iOS and Android versions. A browser preview can behave differently from an installed app. The native simulator lets you check a phone build, and an installed test is useful for important interactions before a public store release.

Where do records live if people use more than one device?

An app can keep simple data on one phone. Newly Backend can provide sign-in, a shared database and file storage for people who need their records across devices. Newly documents separate development and production data. Decide which information belongs in each and when the production backend should be released.

What happens after the build reaches the store?

Newly can upload an iOS build to TestFlight and help put an Android build on Google Play’s internal test track. You still need the relevant developer accounts. On iOS, you complete App Store review submission in App Store Connect. A test upload is a chance to check the app before releasing it.

What do the plan and the code download cover?

Compare the monthly agent-credit allowance with separate store and connected-service costs. Newly lists no ongoing free plan, though eligible accounts may have promotional credits. An owner or admin can download source from the released branch, including any Newly backend code. Keep live data, service access and signing credentials in your handoff separately.

How would you catch a lost recipe before release?

Draw a fictional recipe saved on an iPhone and opened on Android. Decide whether syncing is part of the app or whether recipes stay on one device.

  1. Choose the expected result
    If recipes sync, show the same account finding the same entry on both phones. If they stay local, label that behavior clearly.
  2. Write the native test
    On paper, mark where a simulator helps and which action you would repeat on an installed test build.
  3. Mark the next release gate
    Write down who can upload the test build and who finishes the store submission.