r/iOSProgramming • • Apr 19 '25

Humor My favorite little game xcode plays with us

Post image
172 Upvotes

r/iOSProgramming • • Mar 14 '25

News GitHub Copilot for Xcode is now generally available!

Thumbnail
github.blog
172 Upvotes

r/iOSProgramming • • Jan 11 '25

App Saturday I created my app, CopyNote, two years ago, and here's how much revenue I'm making now

172 Upvotes

Hello fellow devs!

I just wanted to share a bit of my journey in trying to make revenue from my iOS app and get some advice on how to expand to a larger market, especially the US.

I’ve been working on my little iOS app called CopyNote for 2 years now. I often found myself retyping the same phrases or responses when writing emails and responding to messages—like sharing bank account info, addresses, or phone numbers with friends. CopyNote was designed to solve that problem and streamline your workflow with just a single tap.

Key Features:

  • Save Frequently Used Notes: Store texts, templates, images, reminders, or anything else you need to reference often.

  • One-Tap Copying: Insert any saved note with just one tap—no more dragging to copy-paste.

  • Direct Sharing to Social Media: Share your notes directly to social platforms (like Twitter, Facebook, etc.) from the app itself—perfect for quick posts. In fact, many of our users are businesses that frequently share content via Facebook or Instagram.

  • Customizable Shortcuts: Set up shortcuts to make accessing your saved notes even faster!

My Journey to Monetizing:

When I first launched my app, I decided to offer it for free with ads, hoping to quickly build a user base. It worked to some extent—I gained users—but the revenue from ads was minimal.

Next, I pivoted to offering a premium version with no ads and a lifetime subscription. This generated some decent revenue in the beginning, but I started losing motivation to keep updating the app. It became a grind to constantly find new users, and I hit a wall.

At that point, I decided to make the app completely paid after free trail. I knew this might upset some users, and sure enough, I got a flood of 1-star reviews. I expected it, so I didn’t stress about it too much. But over time, the paid model started to pay off, and now I’m at about 200 daily active users and generating $300+ in monthly recurring revenue (MRR).

The challenge now is that most of my users are based in Korea, which is a relatively small market. I’m looking to expand, especially into the US market, but I’m not sure where to start.

If anyone has experience expanding their user base, particularly in reaching new markets like the US, I’d love to hear your thoughts or suggestions. What worked for you? How did you find new users and gain traction in bigger markets?

Here’s a link to the App Store: CopyNote on the App Store

Link to Facebook: CopyNote on Facebook

I’m currently revamping the app and the App Store page with an entirely new design, as well as working on increasing our online presence on social media. Hopefully, this will help with growth.

If anyone’s interested in checking it out or has feedback (especially suggestions for improvement!), I’d love to hear from you. Feel free to DM me!


r/iOSProgramming • • Feb 26 '19

Article Building complex screens with Child ViewControllers

Thumbnail
mecid.github.io
172 Upvotes

r/iOSProgramming • • Feb 20 '19

After rebuilding my app 3 times, many wasted nights, I persevered & completed my beautiful Sudoku app and am giving it away for free. Sharing my experience with you guys!

171 Upvotes

Link to app: https://itunes.apple.com/app/id1451683705

Here's some backstory.

I originally started working on this app last year summer time. While working on it, my code got quite messy and I ended up abandoning it. Then I returned back to it in October last year and started from scratch again. I worked on it for 2 months and I got frustrated again.

This was mostly because I don't have much experience with coding games and code was getting quite messy. Plus I wasn't satisfied with the UI of my app and thought it looked pretty ugly. I was also being too ambitious with the app as I was trying to make it support dual-player where 2 people could play on the same sudoku board. This was quite difficult as firstly it required a server backend, which despite me having backend experience, was quite hard to implement as it needed 2 phones to be always in sync with each other. Also from some additional research, I found that there actually wasn't much interest in dual player sudoku. So my code base was getting super bloated with having to support dual player - something which wasn't even much desired by many people.

Another thing wrong with these 2 prior attempts was that I had wasted a lot of time trying to get Python working on iOS. The Sudoku puzzle generation logic was written in Python (not mine, I was using an open sourced one) and when a new game started, I would run the Python script on iOS, generate a new puzzle and so on. I have described how to do this in one of my reddit comments before. This itself took me about 2 weeks to figure out and was a complete pain in the ass. Plus it also falls in a gray area of Apple's review system as they are usually not too fond if you running such scripts in your app. So it risked getting rejected in app review. The puzzles generated by the python script were also not "hard" enough.

So I ended up scrapping the whole thing.

So I started it again on around January 20th, again from scratch. Fortunately, having built the app to 75% completetion twice already and abandoning it, I had plenty of code logic which I could reuse after some clean up. This also gave me an opportunity to redesign the UI to make it less ugly. Instead of running the python script on iOS to generate the puzzles, I pre-generated 50,000 puzzles (10,000 for each difficulty) on my Mac and included them in my app.

I go by 80/20 law as 80% of the work was pretty much done in 1 week in this third attempt. Then I spent the next week mostly on settings, theme customization etc. I was finally able to finish this app and submitted it. When it comes to such projects, perseverance is the key to completition. I was stuck many times, the UI wasn't up to my self-imposed standards etc. The 3 re-attempts helped me fix those issues and finally get the thing out of the door. Even though I said "wasted nights" in my title, I don't really consider them a waste as I learnt lots of new things in those wasted hours. I think I am content with what I have built and am ready to share it with you guys! Hope you like it!

Link to app: https://itunes.apple.com/app/id1451683705


In case you are curious what differentiates my app from other hundreds of sudoku apps out there:

  1. My opinion is ofcourse biased but I do think I have a nicer looking UI and UX in my app.

  2. Haptic feedback - when you enter a correct or incorrect answer, you feel different vibrations in the app using the haptic engine. I thought this was really required to give a feeling of "small step to success" towards completetion of the puzzle.

  3. Themes and customizations to make the app as close to how you like it as possible. The dark AMOLED themes is my personal favorite as it looks super crisp.

  4. Unfair and Extreme level of puzzles are actually super hard (at last that's my and couple of my testers' experience).

  5. After a game is finished, you get your overall stats like total time spent, best time, average time, overall score, hints used, mistakes made etc. I personally haven't found any other app present all these stats at the end of a game in a "pretty" way.

  6. My app also comes with a graph of how your scores progress over time. As you play more difficult levels, you get more score. Each higher level gives twice the number of points as the previous level.

  7. Sudoku Extreme can automatically pre-fill the notes and auto-remove them when they are used in a row, column or block. I personally encorage disabling this setting and filling it manually as it makes your brain more active! Also if you fill them manually, you get extra points when you finish the game!

  8. The quick fill feature lets you tap-and-hold a number and then simply tap cells and it will fill it with that number.

  9. Numbers show how many instances of that number are left to be filled in the puzzle. When a number has been used 9 times correctly, it hides itself. You can disable this setting if you like.

  10. Pleasing animations when you fill an entire row, column or block as well as when you finish games! I thought this was essential to make the app as engaging as possible.

Anyway, this is obviously my biased opinion about my app. I am curious to hear what feedback you guys have! Let me know if there is any feedback or any questions about the development process!

I plan on sending an update which includes global leaderboards in the app in the upcoming days.

Link to app: https://itunes.apple.com/app/id1451683705

The IAP has been made free for rest of this week. It should show as $0.00 when you try to buy it.

Here's a few extra videos and screenshots of the gameplay: https://www.dropbox.com/sh/jc0ii3ud80go1vy/AADxjTULFv2WvTaH8ZNJClRAa?dl=0


r/iOSProgramming • • Oct 13 '17

Humor I figured someone here would appreciate this

Post image
171 Upvotes

r/iOSProgramming • • Feb 05 '25

Question FAANG interviews for senior iOS role but no iOS questions?

170 Upvotes

I recently interviewed at three of FAANG companies for senior iOS developer roles. Despite having 5-6 rounds at each company, none of them asked me a single question about my iOS experience. It was all LeetCode, leadership questions, and system design. The interviewers weren’t even from my field or familiar with the technologies I use—they were just there to test my LeetCode skills. Honestly, I don’t know what’s going on with this process. Is anyone else facing the same thing in their own field?


r/iOSProgramming • • Apr 18 '23

Discussion Xcode 14.3 is completely unacceptable

170 Upvotes

Latest releases have been in free fall, but the latest has brought:

  • Bugs with cocoapods

  • Bugs in the IDE, for example it doesn't say anything about errors (just "build failed")

  • Bugs with the signing system which exponentially slowed down

  • Bugs with the simulator as in 3/5 times it black screens and I have to close it and reopen it

  • It does whatever it pleases and I've no control on what it's doing

F it I'm programming in scratch

Edit:

  • Also bugs with HSL videos, so if your app streams video from hsl stream (like mine) expected a black screen


r/iOSProgramming • • Jan 28 '22

News Apple adds support for unlisted apps hosted in the App Store, suitable for organizations and private events

Thumbnail
9to5mac.com
170 Upvotes

r/iOSProgramming • • Jul 05 '21

Discussion Tired of Xcode.

170 Upvotes

I don’t know about you, but I’m starting to get sick of it.

First, it’s terribly slow.

  • Opening a storyboard with a single ViewController can take over a minute, and any file I try to open will be a blank screen until it’s done loading the storyboard.

  • But then, just opening a project can take quite a bit of time.

  • Yes, SwiftUI is supposed to be better. But, personally, SwiftUI previews have only ever worked for tiny brand new projects. Then they just start failing.

Second, it’s unreliable.

  • One day it’ll open a project. The next, it’ll (take a long time and) crash trying. But opening said project via right-clicking on Xcode’s Dock icon will work. Go figure.

  • Then, suddenly, at some point while programming, all syntax highlighting will be gone, and auto completion will just stop working, plain and simple.

  • Edit 2: Also, @IBDesignable. It’s a neat idea. If only it worked reliably instead of randomly failing to render.

Third, I find it’s build time errors can be ridiculous.

  • The worst of course, is when using things like RxSwift. But I find the Combine ones pretty hilarious too, sometimes.

Fourth, it’s "refactoring" capabilities are meh.

  • When it does work, and doesn’t just take ages playing it’s accordion animation only to fail cryptically, the renaming refactoring feature will often behave like a simple search and replace, renaming properties from other classes and structures.

Last, weird bugs with more or less helpful logs:

  • Why do we have to wipe the DerivedData so often? It was almost nice and fine until we started adding SPM packages into the mix and they too were stored there. Now, after wiping those, we also have to redownload our dependencies. Yay

  • Did you know there were other folders you could clean up when stuff stops working? There’s xcuserdata in the xcworkspace, also ~/Library/Caches/com.apple.dt.Xcode.

  • And sometimes you have to reboot your Mac because somehow XCode suddenly lost the rights to write into one of it’s build folders. Don’t ask me how; I have no idea

  • Crashes / hanging forever because a device is plugged in / connected "over the network" ? Seems it’s been fixed since. But that was pretty annoying.

Anyway, sorry for the rant. It just gets tiring over time, and sharing with other people who might know that pain makes it feel better.

If anyone has solutions, you are more than welcome.

And if I’ve forgotten anything this godforsaken tool does wrong, you absolutely are welcome to chime in.

Edit: fixed format


r/iOSProgramming • • Mar 27 '21

Application Animated TabBar created using SwiftUI.

170 Upvotes

r/iOSProgramming • • 7d ago

Discussion App Store Review is now automatically rejecting brand new apps for guideline 2.1 - Information Needed - New App Submission

169 Upvotes

I've been developing apps ever since the App Store was created. In my career I have published around 100 apps, both for customers and myself / my own companies.

It has occurred to me that brand new apps, on their first submission, now get rejected immediately under guideline 2.1 - Information Needed - New App Submission. This happened on multiple apps on multiple developer accounts, even on my own account that is over a decade old and never gets any rejections.

Add all of the following information to the Notes field of the App Review Information section in App Store Connect and resubmit your app for Review:

A screen recording captured on a physical device, running the latest operating system, demonstrating the app's functionality. The recording must begin with launching the app and show the typical user flow. If the app has any of the following, include them in the recording:

- Account registration, login, and account deletion flows. Account deletion is required in apps that support account creation.
- Any user-generated content, including the required content reporting and blocking mechanisms.
- Accessing paid content or features within the app.

2. A description of the app's purpose and target audience, including the problem it solves and the value it provides
3. Instructions for setting up and accessing the app's main features, including any required login credentials or sample files
4. A list of the external services, tools, or platforms the app uses to deliver its core functionality (for example, data providers, authentication services, payment processors, or AI services)
5. Describe any regional differences in the app’s features or content, or confirm that the app functions consistently across all regions
6. If the app operates in a highly regulated industry or includes protected third-party material, provide any relevant documentation or credentials to demonstrate you are authorized to provide these services or protected material

So if you want to skip this step, make sure you put the above in your app immediately at the first submission.

I personally think Apple should put this list as a feature in App Store Connect, where you tick all the boxed and add all of this information in an easy way. But I am guessing Apple is experimenting with this to fine tune the process.

This note:

Note: Before submitting, run the submitted build through your own testing and quality assurance process on supported physical devices. App Review is intended for apps and metadata that are complete and ready for App Store customers.

Of course it is expected that your app is complete and ready, but apparently so many people are submitting trash that they have to add it.


r/iOSProgramming • • 17d ago

Discussion [Update] My app clone nightmare is finally getting better thanks to Reddit's advice. Huge thanks to everyone!

Post image
169 Upvotes

A while ago, I posted here about being overwhelmed by copycat apps cloning my app, SquatLock.

https://www.reddit.com/r/iOSProgramming/s/DFHq4tc2hc

Thanks to all the advice and feedback from this amazing community, I was able to take action—and as you can see in the screenshot, the fake apps have gone down significantly!

Huge thanks to everyone who helped me out.

I know other indie devs might face the exact same nightmare, so here is what I did and what I learned from this experience:

  1. Trademark in Japan (My home country)

I’m a developer based in Japan. I already had the registered trademark for "SquatLock" in Japan (it cost around 150,000 JPY / ~$1,000 USD to register).

Because trademarks are territorial (country-specific), submitting a dispute/takedown to Apple for the Japanese App Store was very fast and straightforward—Apple approved name changes/removals immediately. However, foreign App Stores were a completely different story.

2. Dealing with the US App Store (First-to-Use rule)

When cloner devs refused to change their app names outside of Japan, I did some research (shoutout to ChatGPT for the tip). Unlike many countries that strictly follow a "first-to-file" rule, the US recognizes common law trademark rights based on "first-to-use".

When the copycats pushed back on changing their names in other regions, I formally cited and explained this prior use in the US market through the App Store dispute resolution channel. Once I laid that out, they actually complied and changed their names in the US App Store without much further resistance.

3. Consulting a Lawyer & Being Realistic

I did consult with a lawyer about pursuing formal litigation, but the conclusion was clear: legal fees would far exceed what made sense for an app of my size.

Unless the copycats were making massive revenue where damages could be recovered, a full lawsuit wasn't practical (and frankly, low-effort clone apps don't make that kind of money). Focusing my efforts strictly on cleaning up the US and Japanese App Stores proved to be the most realistic and cost-effective approach.

Honestly, some might ask if it's worth putting this much energy into a free app. But I genuinely love what I built, and I couldn't just stand by and watch low-effort clones steal the name.

Once again, thank you so much to everyone who gave me advice on my previous post. Hope this breakdown helps another indie dev out there dealing with the same headache!


r/iOSProgramming • • Aug 03 '21

Application Contact Application created using the SwiftUI Framework

169 Upvotes

r/iOSProgramming • • Nov 10 '20

Article On Apple's Piss-Poor Documentation

Thumbnail caseyliss.com
169 Upvotes

r/iOSProgramming • • Mar 24 '20

News Xcode 11.4 is out now.

Post image
169 Upvotes

r/iOSProgramming • • Jun 17 '15

Apple has published a great free learn to code course for Swift — on GitHub

Thumbnail
medium.com
169 Upvotes

r/iOSProgramming • • Sep 24 '25

Discussion I am designing a simple analog-style camera app in SwiftUI. What do you think?

Thumbnail
gallery
168 Upvotes

I experimented with two background styles, which one would you go for?

  • a solid color (1)

  • a vintage “leathery” texture inspired by real film cameras. (2)

What do you think? I’d really appreciate your honest feedback and suggestions for improvements!

My goal is to keep the app simple and minimalistic, while still capturing the feel of classic analog film cameras. Would you improve or change something?


r/iOSProgramming • • Apr 10 '23

Discussion I Dislike SwiftUI The More I Use it

168 Upvotes

So let me start off by saying I've been an iOS programmer for 6 years and I have been programming on medium to large scale projects mostly, and I have dealt with and developed on both Storyboards, programmatic UIKit and SwiftUI quite extensively.

And when I first lay my hands on SwiftUI I was quite hopeful, it seemed pretty neat! I could write views in a fraction of the time and everything "just worked!". However as time went by and I started to trust using it in larger and larger flows I realized that it's quite limited and frustrating to use, not being able to customize the navigation bar fully is a big hit, And that's setting aside sometimes when View blatantly don't fucking work, I had a View wrapped in a GeometryReader blatantly not render when it did when I removed the GeometryReader, that's kinda wild, I never know if I can actually write a View in SwiftUI because of that.

And I gotta say, the more I use SwiftUI the more I dislike it. I mean, I guess it's fine for smaller scale projects that have simplistic views, some more mildly complex things are also possible, however developing complex screens is still a complete chore.

First of all my biggest pet peeve is animations, I swear every time I want a basic nice animation I have to work like a whole day to make it work, fiddling with where and how I display views, moving ".transition()" modifiers everywhere and so on. UIKit was much more intuitive with human understandable KeyFrames instead of bizarre and abstract interpolations between vaguely related subviews.

Second of all, the interoperability with UIKit is pretty bad, I find myself constantly needing to rewrite UIViews and UIViewControllers in SwiftUI, which takes a lot of time, because they misbehave when wrapped in a UIViewRepresentable and UIViewControllerRepresentable respectively. I also found that if for example you insert a wrapped UIViewControllerRepresentable into a NavigationView, said wrapped controller does not have access to the NavigationView through the navigationController variable, which would have been available if it was pushed unto a UINavigationController's stack. I had to write a Router to solve that issue which is a whole other thing.

Thirdly, and this might be my pet peeve. I find that designing your own generic Views in the way that Apple does them is very difficult as opposed to writing UIViews in an "applyie" way. I hope it makes sense to somebody, but for example, I know how I'd roughly implement a UITableView from scratch if I had to, however I have no clue how I'd implement a "ForEach" type SwiftUI View from scratch.

Anyway what I am saying essentially is that I find writing complex flows and large Views quite tedious and frustrating in SwiftUI.

That's my rant :D


r/iOSProgramming • • Jul 10 '21

Application Spent almost two years creating an application for flatmates, couples and families to organize their household. Includes groceries, finances, chores and more. Please give me feedback!

168 Upvotes

r/iOSProgramming • • May 12 '26

Article App Store Design Cheatsheet (2026)

Thumbnail
gallery
167 Upvotes

After 20 years in the design field (thousands of App Store screenshots and marketing materials!) I consolidated the layout principles, color theory, and simple tweaks behind high-performing screenshots into a single cheatsheet and checklist (it's free). It covers the stuff many of us have to learn the hard way: visual hierarchy, storytelling structure, social proof placement (and how important it is), and why your first screenshot matters more than the other 9 combined.

I've personally implemented these principles to improve App Store conversion rates, some weeks hitting above 10% (more details in the article).

Some interesting "fun facts":

  1. People form visual opinions in as little as 50 milliseconds, and these snap judgments don't change with longer viewing time (your app's first impression really matters)

  2. Most App Store visitors are very decisive: 60% never scroll past the first screenshot before deciding to install or leave

  3. Less than 2% of users tap "Read more" on the App Store description (this surprised me)

Check out the full cheatsheet (it's free): 2026 App Store Screenshots Design Cheatsheet

Happy to answer any questions about App Store screenshot design, A/B testing etc in the comments.


r/iOSProgramming • • Oct 05 '24

App Saturday Finally published an app after 12 years of trying

167 Upvotes

https://apps.apple.com/us/app/my-beautiful-flight/id6736398704

I still remember 12 years ago, when I got my first Mac at 15 and tried to build my very first app. I was so determined, but after a few months, I ended up in tears because I couldn’t understand a thing about coding (honestly, I still don’t that much, thanks GPT!).

Well, here I am, 12 years later (currently unemployed, working full-time on this project), and after countless attempts on different tech and non-tech projects of all types, and many learning moments, I’m beyond proud to say that I’ve just published my very own app!

It’s called My Beautiful Flight, and it’s designed for people who feel anxious about flying. The app includes engaging learning content to help users better understand flying, a 24/7 chatbot for real-time support, and a cool flight tracking feature that keeps you updated on your flights without needing a flight number.

Obviously, this is the very first version, but I can’t wait to hear people’s feedback to improve the app and make it even better!

Thanks for reading, and if you or anyone you know struggles with flight anxiety, I’d love for you to check it out!


r/iOSProgramming • • Jan 06 '24

Question Whats your salary as iOS developer?

167 Upvotes

I wanted to know what is the market like for ios developers around the world. Please mention your country, number of years of experience and your salary.

I will start with mine Nepal, 10 years , USD 2500 / month

Note: I think devs around my country are getting really underpaid. I think I got what it takes. I have even contributed to open source ios project Ice Cubes App.


r/iOSProgramming • • Mar 15 '16

Library Do you need a cache system for your app? We at Spotify just open sourced ours.

Thumbnail
github.com
167 Upvotes