r/iOSProgramming • • Sep 29 '26

Discussion Apple review now rejecting new builds for 1.4 “Physical Harm”

0 Upvotes

Pretty disappointed since my full vision of the app will not be able to be completed on iOS.

Rejected for 1.4 Physical Harm (alcohol related). Released the app 6 months ago. Had about 7-8 updates released since then. But it looks like no more updates from now on.

I made the app for myself and it helped me understand my own drinking, was able to better drink in moderation, never got drunk again since I started using the app. And a lot of people said the same to me. But Apple says “physical harm” lol.

What’s funny is that they aren’t even going to remove the app, just no new builds. App still being downloaded and making money. And plenty of other same apps out there as well, guess they won’t be updating either.

Well time to work on the Android version I’ve been putting off!


r/iOSProgramming • • Sep 29 '15

Question Made a new app, it's growing fairly fast. Worried I can't afford hosting costs?

0 Upvotes

I made a social network app to meet new people. Currently only for iPhone, and it's doing alright. Been out for 4 days now, and I just hit 1,000 registered accounts, and ~40-60 users online nearly all the time. The last 24 hours I've been gaining 40-100 registered accounts per hour.

I don't have ads or in-app purchases in this app, so I'm literally making zero revenue, which I'm okay with. Throughout the whole development phase I knew hosting would be an issue in the future, but I figured if it was something I had to worry about, that would be a good thing.

I chose Parse as my backend. I know a lot of people dislike Parse, but personally I haven't had any problems at all with it. I managed to make a social network that so far, people are liking.

I don't know what it takes to get featured on the App Store, but I'm worried that if I keep getting 50-100 new registered accounts per hour (and growing), that inevitably if it goes viral somewhere, I won't be prepared for the influx of users.

I'm only 19 and I've spent the last several months working on this, and I have absolutely no funds. How do I move forward at this point. Would investors be interested in my product, or do I need to wait longer and become a little more established?

App Store link: http://appsto.re/us/IEsq9.i


r/iOSProgramming • • 12d ago

Discussion I checked 176k iOS apps launched since September. Paid apps get rated at the same rate as free ones, and it's the category that matters

0 Upvotes

I track new App Store releases. In the last 60 days (since Sept 11), 176,508 apps went live and 797 of them (0.5%) have passed 25 ratings so far.

Someone asked in another thread whether charging upfront changes that, and it's a question I'd want answered before picking a pricing model, so I split it out. About 5,000 of the new apps (under 3%) are paid upfront, and 28 of those have passed 25 ratings. That's about 0.6%, basically the same as everything else.

What actually moves the number is games vs non-games:

- Paid games: 21 of 1,171 (1.8%)

- Free games: about 1.7%

- Paid non-games: 7 of 3,858 (0.2%)

- Free non-games: about 0.25%

So within each group, price makes almost no difference. A game is around 7x as likely to get there as anything else, paid or free.

The paid ones that made it are interesting too. Most of the games are ports of console and PC titles (Kingdom Rush 6 with 2,888 ratings, Sifu, Saints Row: The Third, Dome Keeper). The 7 non-games are mostly small single-purpose tools: Chromagraph Camera (193), Deck-Man: Cassette Player (189), TypeDraw (71).

Caveats:

- Ratings are from the US store only.

- Ratings aren't sales. A paid app with 20 ratings could easily be making more than a free one with 200.

- "Free" means free to download. My data doesn't say whether an app has in-app purchases.

If you've shipped a paid-upfront app recently, how did the first ratings compare to free apps you've done?

Full breakdown by category (it's my project): https://storetally.com/apple/reports/launches


r/iOSProgramming • • Jul 29 '26

Discussion Apple killed our whole developer account overnight. 4 families were living from this app.

0 Upvotes

I don't even know how to write this properly, so I'm just gonna write it.

We worked on this app for almost a year. It was doing well. ($100k MRR) Thousands of people paying every month, good rating, people actually using it and staying. Four families were living from this.

Then one day I check my emails. Pending Termination Notice. Everything gone from the store. Payments frozen. Transfers disabled. No warning before, no "hey we noticed something", nothing. Just done.

And the reason they give you is a copy paste paragraph. Something about "misleading purchase flows" and "scareware tactics". That's it. Account wide. They don't tell you which app. They don't tell you which screen. They don't tell you which build. Nothing.

So now what do we do? We sit and guess. We go through every paywall of every app one by one like detectives, trying to figure out what Apple maybe means. And honestly maybe we are checking the completely wrong thing. Maybe the app we suspect the least is actually the problem. We have no idea. Zero. Because they will not tell us.

That's not an appeal process. That's a guessing game and they are holding the answer and refusing to show it.

And the thing is we didn't even fight them. We checked everything ourselves, we found some stuff that maybe could look bad even though nobody was ever trying to trick anyone, we fixed it, we shipped a new build, we wrote to them and explained exactly what we changed. We asked them please just tell us what you found so we can fix that too.

Then we submitted a proper appeal. And they answered 2 weeks later. Meanwhile we are losing all of our customers, receiving tons of emails that our users can't get premium! You know what the answer was? The exact same paragraph. Word for word. The same copy paste. No detail, no new information, nothing about the fixed build, nothing about which app. They read a full appeal and sent back the same text they already sent us.

We also requested a phone call, which is a thing App Store Connect literally offers you. We wrote please just call us so we can talk about this for 5 minutes. No call. Never. Just the same message again.

And here is the part that gets me. In the EU they are supposed to give you the actual specific facts and circumstances when they terminate a business account, and they are supposed to have a real complaint process. This is not me being emotional, this is written down. What we got instead is a paragraph on repeat and total silence.

Meanwhile go open App Store right now for 5 minutes. Real scareware everywhere. Fake "your data will be deleted" popups. Fake countdowns. Subscription traps made by people who 100% know what they are doing. We reported some of them. Nothing happened. Still up today. But us? Small team, real product, people actually renewing for a year, we fix things voluntarily and ask what's wrong? Terminated. No conversation.

And nobody scams their way into thousands of people renewing month after month for a year with a good rating. That is not how scam apps work. Scam apps die in 2 months. Didn't matter.

Anyway I'm done. We are not releasing anything on iOS again. Everything goes to web and Android (I know they are also not that different but fuck iOS...) from now.

And I talked to a lot of devs privately, this is not rare at all, people just stay quiet because they are scared it makes things worse. At some point Apple should ask themselves why small developers are quietly deciding iOS is not worth the risk anymore. (not sure if they care tho)

It's so fucking unfair for developers who are just trying to survive in this huge unemployment pool.


r/iOSProgramming • • Mar 26 '25

Solved! Would you pick this Mac mini for iOS dev?

Post image
0 Upvotes

Hi y'all,

I recently got interested in playing around with iOS development (I've been a native android dev for some time now).

Since my lovely Thinkpad will not cut it, I started looking for a Mac to pick up, and came across this interesting offer

350€, 2018, ram upgraded from 8 to 32 gb. 6 core i5, 512 SSD.

Would you touch such offer, or not even with a 10 meter pole?


r/iOSProgramming • • 6d ago

Discussion I benchmarked the new Apple TV 4K A19 chip

Post image
4 Upvotes

Hey, it's Josh. I make Apple TV apps and I wanted real numbers for how hard I can push each Apple TV 4K.

So this weekend I used Anthropic's best public AI model, Fable 5.2, to build a small Metal benchmark app, then ran it on one A12, one A15 and two A19 units (tvOS 27.2 and 27.2.1). Instead of a score it finds budgets: the most of one kind of work that still holds 60 Hz for 40 seconds. Each figure is the median of 3 or more runs.

What fits in one 60 Hz frame at 1080p (in brackets: after 20 minutes of continuous load)

KIND OF WORKA12A15A19
full-screen passes of a heavy shader3 (2)5 (4)11 (6)
blended full-screen layers75 (58)108 (84)150 (95)
alpha-tested full-screen layers96 (81)132 (107)168 (111)
sprites, instanced27,000 (25,400)42,000 (32,400)55,885 (33,800)
sprites, one draw call each25,500 (23,500)36,500 (28,000)55,612 (34,800)
1,000-triangle meshes, instanced10,000 (9,560)11,875 (11,875)21,000 (18,100)
1,000-triangle meshes, one draw call each9,800 (9,700)12,431 (11,400)20,400 (17,000)

A few things that stood out if you ship on all three:

  • The A12 sets your floor. It holds 27–57 % of what the A19 does, depending on the work.

  • Plan for the 20-minute number, not the first minute. The chip heats up and the system slows it down. After 20 minutes the A19 keeps 61–86 % of its first-minute budget, the A15 77–100 % and the A12 78–99 % (the A12 model has a fan; the other two don't). I measured the slowdown, not the temperature.

  • Draw calls weren't the limit at these counts. One draw call per object held 87–105 % of the instanced budget, across sprites and meshes on all three chips.

  • At 4K, upscaling is what makes room. Passes of that same heavy shader per frame, with 4K output:

RENDERED ATA12A15A19
native 4Knone fits12
1080p, then MetalFX spatial to 4K128
1080p, then MetalFX temporal to 4Knot supportednone fits3
  • Memory is the same on every box. One app gets about 2,098 MB, whether the box has 3, 4 or 8 GB of RAM.

Method, all the charts, the raw data (CSV/JSON) and a version for AI coding agents to use when building apps to understand capabilities and constraints are all at: https://icallwindowseat.com/apple-tv-benchmark

Limitations aside, for my own apps the new chip has made a real difference in terms of what the quality of output I can achieve especially at 4k.


r/iOSProgramming • • May 17 '25

App Saturday I missed engine sound in my electric car, so I built a fun beautiful app for it

Post image
1 Upvotes

Hey all 👋

I’m Dimi, and I'm a software engineer. Some time ago, I switched from a regular car to an electric one and noticed that I missed the engine sound. Surprisingly, it used to help me estimate speed changes without constantly checking the speedometer, and it also added more emotion to my rides.

I looked for existing solutions, but all of them required me to install something on my car, from external speakers to OBD adapters, and that was too much effort for me.

So I thought: the car has speakers and my iPhone has an accelerometer and GPS, so I could estimate the car’s speed and play engine sounds through the speakers. And I decided to try.

This is how the Motion Beats app was born, and I’m happy with the result. It plays a chosen engine-like sound through the car speakers based on current acceleration and speed. While working on it I also understood that it might be fun and decided to add some unexpected sounds.

• It doesn’t require any external hardware, just the iPhone.

• It has 11 engine sounds to choose from so far.

• Some sounds mimic real cars, like a V8, and some are fun and unexpected, like horse gallop 🐎, spaceship 🛸, or even a heartbeat ❤️

• It uses a combination of accelerometer and GPS data for real-time responsiveness.

• Sound reacts to speed and acceleration like a real engine would.

• The app simulates engine and transmission behavior to make the experience more realistic.

• The default Petrol Engine sound is free to use.

• Other sounds are available for a one-time $9.99 purchase.

Personally, I like default sound, V8, the spaceship, digital, and horse the most.

The app is built fully in Swift using SwiftUI and AudioKit. It’s my first time programming in Swift and overall I enjoyed the experience.

Some of the challenges I faced:

• Estimating speed from the accelerometer is not as easy as I expected.

• Generating engine sounds with AudioKit is tricky. I spent a lot of time making and listening to different versions.

• Making it sound good in a car environment is the most difficult part.

• iOS audio API is quite restrictive and doesn't always allow audio to start in the background. And maybe that’s a good thing.

• SwiftUI is the most enjoyable UI framework I’ve worked with so far, but making the app fully smooth and responsive still takes a lot of work.

• Coming from Kotlin with coroutines, I spent a while looking for something like async channels in Swift :)

Motion Beats on the App Store

If this clicks with you and you have any feedback, I’d love to hear it. If you are committed to trying the app and providing feedback, I'm happy to share a promo code (I have 5 available).

I hope you enjoyed my story, happy to answer any questions.

Thank you!


r/iOSProgramming • • Jan 21 '26

Discussion what the hell is this new promo code system bro its so stupid actually

Post image
1 Upvotes

before you could just dump a couple thousand codes with custom set expiration and whatnot into a csv sheet and be good to go with the links it even directly provided so users wouldn't need to manually go to the app store by themselves, now it only gives you the code and you may manually combine it into a link and also bro wdym 100 code limit its my app bro let me do whatever i want with my promo codes.


r/iOSProgramming • • Mar 28 '26

App Saturday (0 AI Code) I built a cozy daily tracker that required a lot of technical problem solving

Thumbnail
gallery
6 Upvotes

After 2.5 months and 11-hour work days, I’ve finally completed my first solo indie project, Stargaze!

It’s an app that lets you track things daily, but reimagined as a grid of stars that periodically sparkle and shine. The app is filled with pretty animations and custom haptics that make using it a really enjoyable experience.

Tech Stack --

This app is completely hand-rolled with no libraries. SwiftUI, Swift, and SwiftData.

Dev Challenges --

Drawing the star grid: I needed to draw 365 to 366 images performantly. Since I was pretty new to SwiftUI, I initially went with the Grid component and for-each-ing 366 images. But in a tab view where each page has its own star grid, this performed terribly, dropping frames everywhere. I then switched to the SwiftUI canvas, where you tell the canvas what object you want to draw, like a shape or image, then you physically move the drawing frame or the canvas itself to where you want to draw it. Figuring out the math actually took a bit of time, but the equation I landed on was [(d - dc) / (n - 1)] * i, where d is the length of the grid in the x-axis, dc is the diameter of image / star, n is the number of stars in the column direction (here, I chose 18), and multiplying it with i gives us the i-th x-axis position for the star.

Next up, finding which star the user tapped based on the tap coordinates: This one involved more math. Initially, I settled on looping through each star, then finding the shortest Euclidean distance between the tap point and the star, giving us the star closest to the tap. But there was a better solution, one which involved using math. Since it’s a grid, I could calculate the stride length -- which is the distance between any two stars (there are two strides, one for the x-axis, and one for the y-axis), then using the following formula for finding the closest star: round((tap-position(x / y) - Rstar) / (stride(x / y)), where Rstar is the radius of the star, and (x / y) is the corresponding x and y direction values. This will give us the row and column position of the star, essentially revealing which star was tapped. I used this to change which star was highlighted and selected.

Finally, I wanted each star on each tab page to have a random rotation: What I could do was initialize a random array of 366 with a value between 0…90 (since it’s a four-pointed star, rotating at an angle beyond 90 makes no difference), but instead I went ahead with a deterministic hash-based solution. This involved taking the unique ID (the UUID) of each habit as a base, then hashing it with the star number that we wanted the angle for, and finally modding it by 90. This allows me to get the same angle for each star every single time, on demand, based on a formula. I used the Hasher() Swift function to make this.

There were many more technical challenges that I had to problem solve in Stargaze, but then this post would go on forever, lol.

AI Disclosure --

NO AI

I’m absolutely against AI-made slop, so Stargaze is made with 0 AI code, 0 AI art, and 0 AI text. All work was done by me, the code was created in Xcode non-agentic mode, the art was created in Affinity and Icon Composer, and the words were created in my head. You can see the proof in the AI-Info section here.

IAPs --

There’s one main IAP in Stargaze, which is a one-time purchase of $4.99 for Stargaze Plus (unlimited habits, custom color for habits, data export / import / custom icons). There’s also a tip jar in Stargaze for any voluntary donations!

It isn’t another habit tracker meant to hold you accountable or make you complete things, just something cute and cozy to look at as you
track something every day :)

Privacy --

None of your data is tracked. Neither is it stored anywhere except your personal device.

Check out Stargaze here! – Stargaze on the App Store
My website (anti-AI slop project): https://hazels.garden

~ Hazel <3


r/iOSProgramming • • Feb 10 '25

Question What's the fastest way to fully develop an IOS app?

0 Upvotes

I currently have experience doing full stack work and some IT skills so I have some experience developing start to finish applications. I have a relatively straight forward idea for an app I know I could build as a Web App but I believe an IOS app will increase the availability significantly.

While I know I could probably go learn swift fully and develop it strictly in a code environment I was curious if there was any IOS software that was similar to Wordpress? For those who don't know what Wordpress is, it is a platform that lets you develop websites extremely quickly and has a very low learning curve. I'm not super interested in spending a ton of time learning swift if my idea does not pan so if I can avoid some of the learning curve that would be great. Thanks!

Edit: Sorry if this felt a little vague. I meant more so if there we're any low code tools that I might be able to utilize to avoid the time commitment of developing basic features and I could spend my time or the more complex task.


r/iOSProgramming • • Feb 01 '25

Discussion There is a serious lack in skills in iOS candidates that I've interviewed. Here's my tips.

0 Upvotes

Looks like a lot of comments don't know how to read: I am NOT grading them a pass or fail on their ability to use Xcode or maximize windows. The point is you're only hurting yourself coding in a tiny window and clicking around letting your clock run down to 0. Interviews have time limits.

I've interviewed several iOS candidates from mid to upper level positions and sometimes I'm just screaming in my mind after seeing so many of them have issues:

* Screen Share Unpreparedness: They are told ahead of time by the recruiter that they'll be doing a live coding interview. When I give them the iOS project and they start sharing their screen, they waste time closing out of a bunch of windows while I just wait for them. It's like they were working on their own project 1 second before the interview. Am I the only one who has a clean desktop when I prepare for an interview? This is an interview! A future career: why not take some time to be ready. I don't count this against them, just that its a waste of time on their end.

* Not Maximizing Window: Almost every single one opens the Xcode project in a window that doesn't even take most of the screen space and gets to work. How do you work like that? They have barely enough space to see one file. And they're sharing their entire screen so maxing the window wouldn't be an issue. I won't take points off but how can you do live coding and keep the window only taking 30% of the screen?? I don't count this against them, just that you're hindering yourself.

* Unfamiliarity with Xcode Shortcuts: 99.99% of the people I interviewed did NOT ever open files side by side. We have instructions + sample JSON they have to look at. They end up clicking back and forth between the files and the Swift files they create. It's a huge waste of time click back and forth. Just open the files side by side. You can hold down option + click a file to open it on the right (or last setting you used). Plus that little button on the top right of the editor to open a window to the right or bottom (hold option down). Another one I rarely see them do is use option + click in the code to get quick documentation so they start opening Apple's docs and searching the class name. Speaking of, only 1 person knew you can open Apple docs from Xcode (Help > Developer Documentation). Everyone else goes to Google. I won't take points off but not knowing how to be proficient makes you waste time.

Speaking of shortcuts, almost nobody uses the file explorer (command + shift + o) and click around looking for their files in the navigator. And having to move code around with copy+pasting with a mouse wastes time. Learn to use command+option+[ or ] to easily move code blocks up and down or command+shift+arrow to select code.

* Not Testing Code: This is probably the biggest problem I see. So many candidates start coding... and coding... making a new file... and coding - without ever building/running the project to make sure it works. Then when they finally do run it they end up with issues across many files. 99% of the people do NOT even run the project when they open it to see what they're given already. Speaking of testing, majority of them don't even use SwiftUI previews - it's odd. They write SwiftUI code, run, wait, redo.

* Too Much Dependence on Google: A lot of people ask me if they can google how to do surface level iOS stuff (decode, List/Table, etc.) You are limited on time on the project. Getting answers from Google will save you a lot of time but doesn't make you look good. Yes I know: we all use Google for work anyway - what's the problem? The problem is if I have an iOS candidate who did NOT use Google at all (and it happens often), then why would we pick you who had to depend on Google? The other iOS candidate would be preferred here. Don't forget: you're competing against other people.

* Reading Errors / Warnings: A lot of times I notice candidates get an error, and immediately assume what the issue is, make a code change, and get the same error. But because they assumed, their new code change generates another error. Take your time: read errors and be familiar with how to address them. I understand getting nervous coding live and sometimes slipping up on simple stuff but read, not just rush to fix without knowing what you're fixing.

* Immediately Coding without Reading All Instructions: Somewhat of a common issue but we give them instructions for the Xcode project. A lot of people skim through it quickly and then start coding and then end up asking questions and get stuck later not realizing everything was given in the instructions. Sometimes they code the wrong direction and I have to steer them in the right way, which doesn't make them look good because they would know if they read the instructions. Take your time.

You might say that we are just filtering candidates wrong but a lot of them have great resumes but we aren't just looking for someone average, just a little bit above average. And yes I do sometimes pass people, but most people I have fail. I've seen these issues for both mid role and upper level roles.


r/iOSProgramming • • Mar 16 '24

Tutorial The correct way to deal with DSA is withdraw your app from Europe

0 Upvotes

Dont compromise on your privacy. You do not need to comply with EU laws if you do not live in the EU . Android is 88% of the market in Europe. It is a relatively very small iOS market. If you don’t make much money there already will not notice a thing if you pull your app from the EU. I am going to ignore the prompt. If you are a small dev, what they are asking is to publish your home phone number and address.

I'm this guy btw. https://news.ycombinator.com/item?id=17095217 When GDPR happened I couldn't guarantee GDPR compliance in my free open source app in time. I pulled this app. I added it later when there was legal clarity. When France required me to submit my e2e crypto details in person in French to an office in Paris, I pulled the app in France. The only losers here are Eu users. Don't lose sleep over Eu laws that do not apply to you,.

Proof you do not need to follow eu laws if you don’t do business there. We have been here before:

https://fortune.com/2018/08/09/news-sites-blocked-gdpr/

Edit: clarification on numbers.


r/iOSProgramming • • Oct 16 '26

Discussion Apple should charge $100 per published app, not per developer account.

0 Upvotes

We really do not need another generic habit tracker or expense tracker on the App Store.

Right now, paying $99 a year gives people a free pass to flood the store with unlimited low effort clones. If Apple charged $100 per published app instead, people would actually have to think twice before submitting another template.

Would this clean up the spam, or would it just hurt devs trying to test ideas?


r/iOSProgramming • • Sep 26 '19

Article Apple’s use of Swift in iOS 13

Thumbnail
blog.timac.org
15 Upvotes

r/iOSProgramming • • Mar 17 '24

Discussion European bureaucracy is creeping in!

9 Upvotes

I maintain a very basic app that requires no login and only gathers simple analytics and crash reports with firebase. I'm trying to upload an update and now I have to upload an approved "French encryption declaration approval form" to release the app in France.

I can only imagine that this form will take awhile to be approved. Not only that, it's extremely difficult to find the bloody form and the website is in... you guessed it... french. I might have to let France go I think.


r/iOSProgramming • • Feb 16 '26

Discussion Xcode 26.3 ai agent Vibe coding ai slop

0 Upvotes

I’m a non coder testing out Xcode 26.3 Claude agent ai , I asked it to create a photo editor and it put out a. Very presentable Mac app, but when i go to export the photo it the app crashes, I asked Claud to fix it multiple Times and it still doesn’t run right. I don’t understand how ai is coming for programmers when it produces garbage.


r/iOSProgramming • • Feb 21 '26

App Saturday Built My First App in Pure SwiftUI — Hit #1 in Developer Tools on the Mac App Store. Here's What I Learned.

Thumbnail
gallery
0 Upvotes

I just launched Devly, a native macOS menu bar app with 50+ developer utilities. Hit #1 in Developer Tools within 6 hours of launch and stayed there for 96 hours.

Tech Stack

  • Pure SwiftUI, zero third-party dependencies

  • Apple native frameworks — CryptoKit, Foundation

  • Full App Sandbox compliance

  • macOS 13+

Development Challenge

The biggest challenge was getting all 50+ tools to work inside Apple's App Sandbox. Retrofitting compliance late in development added weeks to my timeline. I also built a ToolProtocol pattern that every tool conforms to:

protocol ToolProtocol {
    var id: String { get }
    var name: String { get }
    var category: ToolCategory { get }
    func process(input: String) -> String
}

AI Disclosure

Human built. AI used minimally for code completion only, similar to autocomplete. All architecture, design decisions, and implementation are my own.

SwiftUI Lessons Learned

NSPopover is not UIKit Getting the menu bar popover to feel truly native on macOS took way more iteration than expected coming from iOS.

macOS SwiftUI is not iOS SwiftUI Read the macOS HIG before touching any UI code easy to accidentally ship something that feels wrong on Mac.

What I Built

50+ dev utilities in your menu bar JSON formatter, regex tester, color converter, Base64, JWT decoder, bcrypt, UUID generator, diff tool, and more. Everything runs locally, zero internet required, $4.99 one-time.

App Store | Website | All 50+ tools

Happy to answer any SwiftUI or macOS questions!


r/iOSProgramming • • Jan 12 '22

Article Ever wondered how much mobile app downloads contribute to climate change?

Thumbnail
emergetools.com
0 Upvotes

r/iOSProgramming • • Jun 15 '26

Solved! Users complete onboarding but don't do a single workout. Help me read my own funnel

Thumbnail
gallery
1 Upvotes

I'm a solo dev. I built a fitness app with voice-coached workouts and progression tracking, all on-device. I finally wired up analytics and the first thing it showed me is uncomfortable: people get through onboarding fine, then a chunk of them never tap Start on a single workout.

The sample is small so I'm not over-reading the exact numbers, but the shape is consistent enough that I'd rather understand it now than after I ship ten more features nobody reaches.

Right now onboarding is 5 quick screens: a welcome, pick a coach persona, a short fitness profile (training experience + a couple basics), a settings screen (units + default rest timer), then notifications. Then it drops you on the Programs tab, which for a brand-new user is the program library: ~30 built-in programs across 6 categories. You have to pick one and activate it (or create one) before there's an actual "today's workout" with a Start button. There's no first workout queued up for you.

My hypotheses, in no order:

  • onboarding asks for too much before the app shows any value

  • landing on a library of 30 programs is too big a commitment before you've done a single rep, so people don't pick anything

  • too many workout types in the mix (running, HIIT, lifting, etc.) and people don't know which to choose first

  • a lot of installs are just curiosity and the person was never going to train in that moment

What I'd find most useful: look at the flow in the screenshots with fresh eyes and tell me where you personally would drop off before the first workout. And if you've shipped anything with a "get them to do the core action once" funnel, what actually moved it?

Screenshots of onboarding and the home screen below. Happy to send a TestFlight build if you want to poke at it, just say so.

Not pitching, hence no link. I just want to fix the funnel.


r/iOSProgramming • • Jun 10 '24

Discussion OpenAI integration for Siri seems like a cop out… how do you feel?

4 Upvotes

I have been wanting a Siri upgrade for what feels like forever… I stopped using it because most of the time it would just say “here are some safari results”

I wished Apple would’ve spent its time creating its own in-house AI instead of partnering with OpenAI, even if it was slightly better than the current Siri I would’ve appreciated it knowing that they are going to improve it… imagine telling Steve Jobs that Apple probably paid millions to integrate a Microsoft owned service into its devices…

But I want to know what you guys think! Love or hate it? Think it will be useful?


r/iOSProgramming • • Mar 10 '26

Question I just starting experimenting with native Swift development, is XCode usually this atrociously slow to use? It's driving me insane, errors take a minute or two to appear in what is a very simple app.

7 Upvotes

Compared to Android Studio, this IDE is barely functional. And don't get me started on "The compiler is unable to type-check this expression" error, it's like an IDE saying "there's an error in these 100 lines of code, figure it out yourself I'm out"

Edit: thanks to the helpful comments, I kinda understand why this happens. The unresponsiveness and delays are actually related to that error, once it is eliminated the rest of the errors and code update responsively.


r/iOSProgramming • • Sep 13 '26

Discussion In the age of AI, when generating an iOS app is cheap, what part of designing one is still hard?

0 Upvotes

For developers designing their own apps, what do you still struggle with most?

- Choosing the right interaction pattern
- Knowing what “good” iOS UX looks like
- Motion and transitions
- something else?

Curious whether design judgment is becoming more valuable as implementation gets easier.


r/iOSProgramming • • Jan 10 '18

The Ultimate List of Resources for iOS Devs

Thumbnail
youtu.be
6 Upvotes

r/iOSProgramming • • Aug 27 '24

Discussion What is the hard part?

0 Upvotes

iOS Development looks straight forward due to swift and SwiftUI but where it the hard part? Like what takes the most time and nerves?