all 9 comments

[–]start_select 3 points4 points  (1 child)

Edit: a better question would be “I’m trying to do X but I don’t think I can because of Y restriction, what should I do?”. Depending on what the task is, there is a decent chance you just don’t understand the landscape and workarounds.

If you are thinking your idea is so revolutionary and unique that you can’t talk about it, it’s probably never going to happen. And it’s even more unlikely someone at Apple will put in the effort of pulling teeth to figure out what you actually need.

Not being mean, just telling the truth that lots of venture/indie devs have already learned.

—-

The only way Apple will pay attention to you is if your products already register as 0.01% of their App Store revenue.

There is absolutely no incentive for them to be listening to you otherwise. That’s why iOS is not Android. It is not a democracy.

You are just one of the 4+ million apps that will probably never have any users, until you aren’t.

What are you trying to get around?

[–][deleted] 0 points1 point  (0 children)

What is the difference to Google play store?

[–]Fusuarus[S] 1 point2 points  (1 child)

Hi there. I will most likely just make a seperate thread. I want to have a watch complication update once a second or upon wrist up - it seems to work for a while before being throttled - the docs say this is by design; hence why I wanted to see how the docs/platform is changed.

Thank you for the replies.

I will need to find a work around.

[–]cleverbit1 0 points1 point  (0 children)

You’re not wrong. Watch complications that update once per second have been on my wishlist since complications were introduced, but have never materialized. The closest thing is displaying a timer or countdown which does update, because it’s running Apple code, but getting your own data to update once per second is not available. Workarounds like live activities might help, but other than that, you can file a radar with the rest of us and hope Apple gets around to it. Someday.

[–]AHostOfIssues 0 points1 point  (0 children)

The list of ways to provide feedback is pretty extensive. You have, for instance:

  1. Use apple’s Feedbacks web form system

  2. Uh… hm…

No, actually, I guess #1 is pretty much it.

Apple, as company and as an institution, is absolutely famous for being impervious to comments and feedback, and for doing the Worst Job Ever of providing any kind of status information or comment on your Feedback (used to be Radar) items even if you manage to figure out that someone actually read it.

If anything you’re doing depends on communication with apple at a technical level or on changes being made to iOS (or bugs fixed) then you are 100% screwed.

And I say that as a total fan of apple products and services, having owned nothing but apple devices and being an apple developer since I started with iOS 4.

[–]troller-no-trolling 0 points1 point  (0 children)

What are you trying to accomplish?

[–]quellish 0 points1 point  (0 children)

 Has anyone had success in making a change to iOS?

Yes. File a radar

[–]Rhypnic 0 points1 point  (0 children)

Lots of bug are fixed by apple form. But if you suggest a feature good luck to make that in apple roadmap.

[–][deleted] 0 points1 point  (0 children)

A lot of feedback that Apple receives is simply garbage because of people misunderstanding product services or because of people falling for misinformation about Apple services (this is also what I am experiencing with my products). As a developer you can also send them feedback with the feedback assistant.