I have to be honest: Just a year ago, I would have laughed if someone had told me that I would be publishing an iPhone app in the Apple Store. I am Cristiano Rego, Solution Engineer at CNEXT, and my world has been Microsoft Power Platform – Power Apps, Power Automate, Dataverse. Native app development? That was always "the other side" for me.

And then came Replit.

The Idea: Why an iPhone App at All?

At CNEXT, we work daily with clients who want to digitize their business processes. Many ask, "Can we also have this as an app in the App Store?" With Power Apps, we can build great business apps – but a real, native app in the Apple App Store? That was a whole different league until now.

I wanted to prove that you can build and publish a real iPhone app without years of Swift or React Native experience. The idea: A tool that helps our clients in their daily lives – directly on the iPhone.

Getting Started with Replit: Easier Than Expected

Replit changed everything with mobile app support. I could set up a React Native app directly in the browser – without installing Xcode, without macOS-specific toolchains, without hours of configuration.

What Surprised Me:

• No local setup required: Normally, you need a Mac with Xcode, provisioning profiles, and developer certificates. Replit takes care of a large part of that for you.
• Live preview on the phone: I could see changes immediately on my iPhone – this accelerated the development process significantly.
• AI-assisted coding: The Replit Agent helped me write code that I, as a Power Platform developer, would never have written. From React Native components to navigation and state management.

The Challenges: It Wasn't a Walk in the Park

I don't want to sugarcoat anything – the path was rocky. Here are the biggest challenges:

1. The Apple Developer Program

Before you can even submit an app, you need an Apple Developer Account. This means:

• 99 USD per year – not exactly cheap for an experiment
• Identity verification – Apple checks exactly who you are
• Waiting time: For me, the verification took almost a week
• D-U-N-S number for companies: If you publish as a company, you need a D-U-N-S number – that can take weeks again

2. Certificates, Provisioning Profiles & Signing

This is the part that drives most developers to despair:

• Create Development Certificate
• Distribution Certificate for the App Store
• Provisioning Profile for the app ID
• Register App ID in the Apple Developer Console

Replit simplifies much of this, but you still need to understand what’s happening. A wrong profile, and the build fails – without helpful error messages.

3. Setting Up App Store Connect

This is where it gets bureaucratic. Apple requires:

• App name and subtitle (must not be misleading)
• Choose a category (Productivity, Business, Utilities, etc.)
• Set age rating (fill out a questionnaire)
• Privacy policy URL – yes, you need a real Privacy Policy
• Support URL – a contact page for users

4. The Dreaded Screenshots

This was one of the most time-consuming parts. Apple requires screenshots in exact resolutions for different devices:

For each size, you need at least 2, a maximum of 10 screenshots. And they need to look good – Apple rejects apps with poor screenshots.

My Tip: Use a tool like Figma or Screenshots Pro to enhance the images with device frames and marketing text. Plain screenshots without context are quickly rejected.

5. The App Review Process

The notorious Apple Review. My app was rejected the first time. The reasons:

• Lack of functionality: Apple felt that one feature did not have enough "substance." They don’t want wrapper apps that only display a website.
• Unclear privacy information: I hadn’t specified clearly enough what data the app collects.

After revising, the app was accepted on the second attempt. The review took about 24-48 hours – significantly faster than the legendary 2 weeks of the past.

The Apple Store Requirements in Detail

For anyone who wants to try it, here’s the complete checklist:

Mandatory Requirements:

• App Icon: 1024 x 1024 pixels, no transparency, no rounded corners (Apple adds those themselves)
• Screenshots: At least 2 per device category (see table above)
• App Preview Video (optional but recommended): Up to 30 seconds, shows the app in action
• Description: Maximum 4000 characters, clear and honest
• Keywords: Maximum 100 characters, comma-separated
• What's New Text: For updates – what has changed?
• Privacy Policy URL: Must be publicly accessible
• Support URL: Contact option for users
• Build: Must be uploaded via Xcode Cloud, Transporter, or Application Loader

Common Reasons for Rejection:

1. 1Guideline 4.2 – Minimum Functionality: The app must provide real value
2. 2Guideline 5.1.1 – Data Collection: Privacy information must be exact
3. 3Guideline 2.1 – App Completeness: No placeholder content or "Coming Soon" pages
4. 4Guideline 4.0 – Design: The app must follow Apple’s Human Interface Guidelines
5. 5Guideline 2.3 – Accurate Metadata: Screenshots and description must match the app

What I Learned

Replit as a Game-Changer

Replit has democratized entry into native app development. As someone coming from the low-code world, I was able to:

• Build a functioning app in weeks instead of months
• Complete most of the development without Mac hardware
• Write AI-assisted code that meets professional standards
• Test iteratively through the live preview feature

The Apple Hurdles Are Real

One underestimates the administrative effort. Pure development time was maybe 40% of the total project. The rest: creating screenshots, writing descriptions, formulating privacy policies, implementing review feedback, managing certificates.

The Moment of Truth

When I received the notification "Your app is now Ready for Sale" – it was indescribable. My app. In the Apple Store. Next to the big names. Built by a Power Platform guy who couldn’t write React Native code a year ago.

Conclusion: Anyone Can Publish an App

The days of needing a team of iOS developers are over. With Replit and the right perseverance, anyone can publish an app in the Apple Store. Yes, the Apple requirements are strict. Yes, the review process can be frustrating. But that’s exactly why an app in the Apple Store carries so much weight.

My advice: Just start. The biggest hurdle is not the code – it’s the first step.

Questions? Write to me: cristiano.rego@cnext.ch – or just ask me in the office. I’m the one with 40 Nespresso capsules a day. ☕