patrykkosieradzki.com
📱 Senior Android & iOS Dev
📚 Sharing knowledge and best practices
🚀 Full-time dev, building indie apps on the side
32 posts
16 followers
5 following
Regular Contributor
Conversation Starter
comment in response to
post
Curious how backend-driven mobile apps can save you time and money? Subscribe to my free newsletter for more: mobiledevnews.com
comment in response to
post
Numbers alone don’t define a success. Popularity != best choice.
The right tool depends on the project, team, and long-term goals. Pick what works for you, not what’s popular. No need to worry about the FOMO.Â
_______
Follow me for more on Mobile Development
comment in response to
post
- Documentation gaps needing clarification
- And many more.
We don’t know what’s the real cause.
2/ More and more devs now ask LLMs like ChatGPT, Claude AI or Copilot instead of Googling or using Stack Overflow, making metrics like this less relevant.
🧵↴
comment in response to
post
Well, let’s be real. It’s not that simple…
1/ More questions don’t necessarily mean more popularity. Could they mean growing adoption? Sure. But at the same time they might indicate:
- Framework complexity causing more issues
- New devs asking duplicate questions
🧵↴
comment in response to
post
Swift and SwiftUI numbers are slowly increasing. How do you think these numbers will grow in future iOS versions?
_______
More on that in the latest newsletter issue: mobiledevnews.com/issues/51
comment in response to
post
As for the SwiftUI-based app lifecycle, it’s catching on fast:
- 4 apps used it in iOS 16
- 17 apps in iOS 17
- Now, 19 apps in iOS 18
🧵↴
comment in response to
post
Found this post interesting? Follow me for more
comment in response to
post
The goal here was to have full native experience and support. It’s not very complex, so web or pwa is doable, but the ux would be a little different, than what I’m planning to do here 💪
comment in response to
post
Thanks for your feedback! 🙌
comment in response to
post
The worst part about SwiftData is that with its API it makes you need to move data observation and handling into the SwiftUI view, rather than keeping logic in the business layer
comment in response to
post
Yup, every tools has its purpose 💪
comment in response to
post
👋 🇵🇱
comment in response to
post
So the answer is yes and no at the same time 😅
The `task` modifier itself is a UI dependency, but the `Task` is part of the Concurrency package, which is usually considered as business code
comment in response to
post
All these modifiers are just tools that Apple introduces to make iOS Development more accessible for beginners. All of them have their use cases in real world scenarios, like creating personal project or learning, but not all of them are meant to be used in bigger codebases and production
comment in response to
post
The `Task` itself is a business dependency - as it's a part of the Concurrency package. The best case scenario for a "stupid", declarative view is to output triggered events and consume a state to display 👌