They are not testing for usefulness.
Only what their app store rules say (and sometimes only part of it - once your app is established well with them)
Comment on Submitting an App for iOS approval
nix98@lemmy.world 3 days agoThis costs me not just time, but money. I know it isn’t much but is really a big pain. The biggest issue is that the app and recommendation algorithm isn’t going to be useful with 20 songs. You really need 1000s of songs to actually use the app…
They are not testing for usefulness.
Only what their app store rules say (and sometimes only part of it - once your app is established well with them)
For the money angle, something like a Digital Ocean droplet would be appropriate here. They are $4/mo and you don’t even need to run the thing all the time, just when you need an app version approved.
Oracle Cloud offers 4 ARM cores, 24GB RAM and 200GB storage in their free tier (IIRC you can even divide that into 4 separate VMs). Very useful for cheap testing, if your code/server supports ARM.
Even then, a small underpowered x64 VM for testing purposes is often free on all hyperscalers. Not the fastest server, but depending on the use case?
I don’t want to be the asshole but 3 days of a super underpowered VM (it can be a oracle free tier for example) is a drop in the ocean compared to the $100/year/perpetuity that apple wants from devs
Main problem might be the content, as they might think that it’s going to be used for piracy
Maybe try to spin it as “Kevin macleod recommendation engine” by filling it with this content archive.org/details/…/1up
BombOmOm@lemmy.world 3 days ago
You don’t need to give them a premier experience, you aren’t trying to sell them on the features of your app. It just needs to function.
Load in those 20 royalty free songs and let the algorithm suck at picking the next of the 20.