It's a bummer obviously, but is there an actual reason not to just use the website?
- you can have personalisation in the app without needing to create an account
- can have access to location without asking the user every time
21–30 of 364 posts
It's a bummer obviously, but is there an actual reason not to just use the website?
- you can have personalisation in the app without needing to create an account
- can have access to location without asking the user every time
Apple shouldn't be the one to tell me what kind of apps I can have on the device I've bought with my money.
Apple, by walling their garden, have essentially used their hegemony to steal billions of dollars in potential revenue from developers. Think of how much innovation has been blocked by them intentionally gimping iOS Safari to prevent web apps from competing with native ones. Remember this when reviewing job applications, folks. Apple, Google, and Facebook employees, current and former, are morally derelict and have p…
I find your sense of entitlement morally derelict.
If the mafia doesn't like your store, you can't offer your product.
They've done this since the early days of the app store. Mostly-content apps without really broad appeal have long carried a high risk of rejection. > Homescreen widgets: utterly useless, but can't get more iOS-y and less webapp-y than this, right? This especially, but really the whole post reads like the system working as intended. Granted (as the author notes) way too much shit gets through anyway, but that's not a…
Tarting it up with shit that no one wants or needs doesn’t change the fact that this would be just fine as a web page.
Ran into the exact same problem with a very simple camera app I made. Camera app was completely gesture based. So you never had to find a button to quickly flip the camera to the other side of the phone or find the button to start/stop recording. It made using a camera a lot quicker to get multiple shots of a scene and your reaction shot. Also added in stabilization to the front lens, which was easy but wasn't enable…
Yep, I got this rejection when I made this tipping app ( https://apps.apple.com/us/app/tip-69/id1460610078 ). I went on to add OCR detection for receipts so you don't have to type in the amount, I added more tipping modes, I added split bill functionality, and eventually added an entire social network with the ability to share your receipt for the world to see, like or comment on. Must have spent months trying to get…
Ran into the exact same problem with a very simple camera app I made. Camera app was completely gesture based. So you never had to find a button to quickly flip the camera to the other side of the phone or find the button to start/stop recording. It made using a camera a lot quicker to get multiple shots of a scene and your reaction shot. Also added in stabilization to the front lens, which was easy but wasn't enable…
The biggest problem I try to convey is that you have no way of knowing you'll get the rejection without putting the work in first.
So you, like me, wasted probably days (if not weeks) to create a fully functional app, spent much of that time on user-facing functions that you would have probably not needed, only to find that it was for nothing.
It's not like on Android where you can just share an APK with your friends.
TestFlight still has to review your betas, if you want to at least share the app with someone else.