I'm Cristiano Rego, Solution Engineer at CNEXT, and until now my world has been the Microsoft Power Platform: Power Apps, Power Automate, Dataverse. With Replit, I built my first native iPhone app and published it in the App Store. The code was the smaller part: the Apple account, certificates, screenshots, privacy details and a rejection in the first review took more time than the development.
Why a native app
At CNEXT we work every day with customers who are digitalising their business processes. Many of them ask: ‘Can we have this as an app in the App Store too?’ With Power Apps we build business apps. Native app development, on the other hand, had always been ‘the other side’ for me.
I wanted to show that you can build and publish an iPhone app without years of Swift or React Native experience. The idea: a tool that helps our customers in their daily work, right on the iPhone.
Developing with Replit
Replit offers a web-based route to native iOS apps: with Replit Agent, a preview in Expo Go and guided submission. I was able to set up a React Native app directly in the browser, without installing Xcode and without macOS-specific toolchains. I did most of the development without a Mac.
What surprised me:
- No local set-up: normally you need a Mac with Xcode, provisioning profiles and developer certificates. Replit takes care of much of that.
- Preview on my own iPhone: I saw changes on the device straight away, which sped up development considerably.
- AI-assisted coding: Replit Agent helped me with code I would never have written that way as a Power Platform developer, from React Native components to navigation and state management.
What took the time
The Apple Developer Program
Without Apple Developer Program membership, you cannot publish in the App Store. Apple lists the fee as 99 US dollars a year, or local currency where available. Then there is the identity check: mine took almost a week. If you publish as a company, you also have to verify the organisation's legal identity, which requires a D-U-N-S number. Requirements and processing times depend on the account; sort these points out early.
Certificates, profiles and signing
Development certificate, distribution certificate for the App Store, provisioning profile, registered App ID: Replit simplifies much of this, but you still need to understand what is happening. One wrong profile and the build fails, without a helpful error message.
App Store Connect
This is where it gets bureaucratic. App Store Connect asked me for:
- an app name and subtitle that are not misleading
- a category, such as Productivity, Business or Utilities
- an age rating, set via a questionnaire
- the URL of a publicly accessible privacy policy
- a support URL where users can get in touch
Screenshots
The screenshots were one of the most time-consuming parts. Apple requires them in set sizes for each device and currently accepts one to ten screenshots per supported platform page. The accepted sizes change as new devices appear; Apple's current screenshot specifications are the reference. My tip: prepare the images with a tool such as Figma or Screenshots Pro, adding device frames and a short caption. But the screenshots and description must match the app.
The rejection
My app was rejected in the first review, for two reasons:
- 1Not enough functionality (guideline 4.2, Minimum Functionality): Apple felt that one feature lacked substance. Apple does not want apps that only display a website.
- 2Imprecise privacy details (guideline 5.1.1, Data Collection): I had not stated precisely enough which data the app collects.
After I reworked both points, the app was accepted on the second attempt. The review took about 24 to 48 hours in my case; neither that time nor the outcome is guaranteed.
When the message ‘Your app is now Ready for Sale’ arrived, it was a special moment: my app in the App Store, built by a Power Platform developer who a year earlier could not write any React Native code.
What I learned
- Apple's hurdles are real: pure development time was perhaps 40 per cent of the project. The other 60 per cent went into screenshots, descriptions, the privacy policy, acting on review feedback and managing certificates.
- Replit lowers the barrier to entry: coming from the low-code world, I was able to build a native app and keep testing it on the device.
- Just start: the biggest hurdle is not the code but the first step.
What to keep in mind
- Review generated code: data access, third-party SDKs, authentication, error handling and accessibility all need checking before you submit. Test on supported devices and with realistic accounts before production data is involved.
- Match privacy details to behaviour: Apple requires an accessible link to the privacy policy. The data, purposes, sharing and deletion periods it describes must match what the app actually does, as must the App Privacy labels and the data collected by embedded SDKs. This is exactly where the second reason for my rejection lay.
- Keep metadata truthful: the App Store page must describe the app accurately.
- Read the current rules: Apple's requirements and Replit's features change. The current App Review Guidelines are what counts.
Sources: Replit: build native iOS apps on the web · Apple Developer Program · Apple: user privacy and data use · Apple: screenshot specifications · Apple: App Review Guidelines

