Articles

Many iOS devs believe they will earn a raise or get paid more if they work longer hours. But it rarely works because...

Have you ever had doubts or difficulty modularizing your iOS apps' architecture? For example... 👇

Ever had to implement a very complex iOS app flow?

Have you ever felt like managing app state keeps getting more and more complex as you add new features? Curious about what design patterns and techniques can help?

Testing simple outputs like Strings or Integers is easy in Swift. What about testing iOS app features that produce complex outputs like images?

Have you ever felt lost trying to measure and solve performance issues in your iOS apps? Curious about how the "Profile" option on Xcode can help?

Ever wondered how many iOS teams keep releasing app versions continuously with confidence?

This iOS developer received job offers from Meta and Apple. Want to see one of the steps in his preparation?

iOS app navigation can lead to high coupling between features. Have you ever wondered how senior iOS devs handle navigation in large modular apps?

Have you ever felt like Apple frameworks such as StoreKit for in-app purchases are hard to use and complicate your code? For example, you may have to deal with many confusing optional properties (that should never be `nil`). Or callbacks with optional results - even though there's no reason to ever get `nil` back in your specific case.

Did you know there are common strategies senior devs use to architect and develop identical SDKs in iOS/Swift and Android/Kotlin? Watch this mentoring session now to learn more.

Many iOS apps lose user data because of bad Core Data migrations. The app may not even open anymore (💥 crashing on startup!). The common user response is to delete the app and leave a bad review. Don't let it happen to you!