App Store release for iOS/iPadOS, funded by optional donations or a low-cost paid download #927
Replies: 2 comments 3 replies
|
Hi thanks for the clear and well thought out message 😄 . I have been thinking about the options as well. And while I would love for the donations to work out it's probably not going to cover the costs. Which is also not the point but still that would have been great. So my conclusion was similar to yours. Either a upfront fee for iOS, but keep the .ipa release free for everyone. Another option would be to have the app be free but have certain features locked behind a "slightly" bigger single purchase or a low monthly fee. Both seem like pretty common options. Just slightly doubtful about which road I want to take. |
|
Just to add, I would like to suggest an official release on a sideloader like altstore for users in the EU and Japan. I think this would be beneficial for the time being to at least get more recognition for this marvelous app. I honestly think this is probably the most polished client for self hosted media servers and the uniformity across platforms is commendable. I think the release on sideloader platforms would also serve a litmus test for the number of downloads to figure out if a subscription or small upfront fee for the app would be feasible for a full release on the iOS app store. |
Uh oh!
There was an error while loading. Please reload this page.
Summary
I would like to suggest an official iOS/iPadOS App Store release for Fladder, supported in a simple way that helps cover the Apple Developer Program fee and ongoing store related costs.
The goal here is not heavy monetization. It is just to make official App Store distribution possible in a sustainable way. A few possible models could work:
• optional donations
• a one time low cost paid app
• a small “supporter” purchase model to help offset publishing costs
This would make Fladder easier to install, easier to recommend, and easier for iPhone and iPad users to keep updated.
Fladder is already a cross platform Jellyfin frontend built with Flutter, so having an official iOS App Store option feels like a natural extension of that cross platform goal.
Basic Example
A useful comparison is Conduit, an open source mobile client for Open WebUI. Its repository explicitly tells users they can install it from the App Store or Google Play, which shows how an open source companion app to a self hosted service can still have official mobile store distribution. 
What I am suggesting for Fladder is something similar in spirit:
• keep the project open source
• provide an official App Store build for convenience
• use optional donations or a small purchase price to help support Apple account fees and release maintenance
This could lower friction for iOS users and make the app more approachable for less technical users.
Drawbacks
There are some real drawbacks and impacts:
• Publishing on the App Store creates an ongoing annual cost because of Apple’s developer fee.
• App Store distribution adds maintenance overhead, including store submission, compliance work, testing, and handling review requirements.
• Even a very small paid price may be unpopular with users who prefer every distribution method to remain fully free.
• Once money is involved, even in a small way, users may expect faster support, more frequent updates, or stronger guarantees.
• Store policies could also affect how some features or release workflows are handled.
Unresolved questions
No response
Implementation
All reactions