Thank you. This is really needed. Have you considered having community supplied component library? Also have you considered premium elements that are richly documented? The official Apple docs are poor so it would definitely be worth a premium to get access.
The vast majority of iOS development is the same stuff over and over with slightly different colours or backgrounds or effects. If you could get navigation, onboarding/login/password reset screens, maps, api queries bound to components, you’d have 80% of the app and developers could instead focus on the critical bits that add real business value. I’ll definitely follow your project.
The current app structure does not allow for community components. Not even for components created by me... But it's a good idea I didn't think about.
At the moment, it's all pretty straightforwardly coded. I first aimed at having an MVP in the app store, so the functionality for the app is now limited. In my roadmap though components will be rearrangeable, allowing for more complex UIs and I am evolving the codebase in that direction.
The rest of what you mention is indeed in my plans. The idea is exactly that: too much time is spent on those same things.
