11 ms·
Apple introduces Ask Apple for developers
- aaaaaaaaaaab 4y agoHow about instead fixing any of the hundreds of well-documented bugreports raised by your developers instead?
- jbverschoor 4y agoStopped submitting those. Takes way too much time to gather everything relevant and not get any response. Apples software quality is pretty shitty these days
- aaaaaaaaaaab 4y agoI stopped too, after they threw back some of my reports because they were missing some completely unrelated generic diagnostic info (like which MacBook generation was I using, even if the bug was 100% reproducible everywhere), even though I’ve provided them a minimal working example on GitHub, and even the method name of the problematic private API.
- pram 4y agoClassic help desk tactics so you don’t have to do any work lol Ah well, this JIRA field was empty can’t do anything about it. WONTFIX
- barbariangrunge 4y agoThis might be great, but who are the “apple experts” you get to be in contact with? It makes me think of the unnecessary logic board replacements their experts (“geniuses”) at apple stores always want you to do, at roughly the cost of a new machine
- Bilal_io 4y agoThe real issue: a small bug. Apple developer: we'll need to rewrite this service from scratch.
- moffkalast 4y agoMust've been a Rust developer working undercover
- saagarjha 4y agoDTS and engineers. It’s similar to a second set of WWDC labs.
- melony 4y agoUsually interns or juniors. The product managers rarely show up.
- spfzero 4y agoGlad of that actually. As a software developer, I would rather talk to the developers.
- LeoPanthera 4y ago> It makes me think of the unnecessary logic board replacements their experts (“geniuses”) at apple stores always want you to do I've literally never heard of this, and I've had several repairs via the genius bar.
- anonymouse008 4y agoNo mention of Quinn the Eskimo - highly suspect.
- jshzglr 4y agoYou all sound so angry. Relax and move on. From this article and from apple apparently.
- hackish 4y agoAt the time of my reply, there are 11 comments with only one being overtly negative (towards bug report resourcing). The post is less than 25 minutes old. Surely we can afford HN more time than that to move on?
- duxup 4y agoI suspect the comment you're replying to is also thinking of other posts, but if so, yes that makes it confusing too. You're response is no less accurate. Personally I do tire from the <insert pet gripe about X company in the announcement> and general pessimism around HN. I'd much rather hear about what folks think of the specific thing and less about the ongoing conversation about topics surrounding the company. So I kinda get that sentiment.
- nixpulvis 4y agoI've been trying to move on from Apple for over half a decade now. There's just not good alternatives in my opinion. :( Plus a lot of my stuff is locked up with them and I don't have the time to migrate all of it right now. Specifically, music is a big issue for me.
- prange 4y agoThis seems to be a common position, but a weird one. It seems like you are saying Apple is the best, but you are mad at them, even though nobody can do better.
- deleted 4y ago[deleted]
- dmitriid 4y agoHow is it weird? They can be both better and bad. It just means that everyone else is worse.
- guyzero 4y agoI'm disappointed this isn't a new voice agent from Apple.
- layer8 4y agoLet’s hope it’ll be more useful than Siri.
- ajkjk 4y ago"We’ve been listening to feedback from developers around the world about what will be most helpful to them as they build innovative apps" Lol, the feedback is surely "stop deleting all your documentation without replacing it" and also "please don't make me re-download Xcode for 3 hours using an account I forgot the credentials for in your terrible app store with its unresumable download flow... before I can do anything", but they came up with this?
- masklinn 4y agoSurely "why is radar a black hole of suck" is in there somewhere?
- x0x0 4y agoIt's absolutely not. Apple desires quick and easy fixes. Devoting time to good documentation, product support, caring about bugs, and devrel ... not gonna happen.
- yamtaddle 4y ago"Make it so I don't contemplate self-harm and/or abandoning my life to live in the woods every time I need to update XCode" would indeed be a big improvement. IDK WTF they're doing wrong with that but god damn.
- fn1 4y agoI suspect it has to do with APFS doing snapshots to be able to rollback an installation and those snapshots being gigantic.
- saagarjha 4y agoNot really. The App Store installation first scans the entire bundle before installing the bits it needs, then it downloads the update and applies it, which goes through some not-very-optimized installation code that compresses the bundle on disk using zlib. This is ok for normal apps but for Xcode this can take a while. Blowing away the entire directory and just installing a fresh copy is usually far faster, if you optimize this you can do it in under five minutes.
- smoldesu 4y ago> Developers can ask for [...] help with App Review Guidelines and distribution tools. This bit is really interesting. It's not a solution to app distribution woes on iOS and macOS, but it is a response to the outcry from developers wanting more clarity on App Review Guidelines. It would be really nice if they could ratify these guidelines as a more consistent set of universally-applicable rules, but I guess an audit session with your local Genius is the next best thing.
- nikanj 4y agoDevelopers can ask. They probably won't get useful answers. But they can ask!
- saagarjha 4y agoI got very useful answers when I scheduled an appointment. YMMV.
- squeaky-clean 4y agoYou managed to schedule an appointment and get time to meet someone today? The service just launched a few hours ago.
- shadowfacts 4y agoThey probably mean at WWDC, where App Review-related appointments are also available.
- saagarjha 4y agoThey did this last year too.
- deleted 4y ago[deleted]
- amelius 4y agoIs this like Nvidia's forums, where employees also respond to questions?
- diskzero 4y agoI may be an anomaly, but most of the Ask Apple topics wouldn't be terribly useful for me. In general, I haven't had much difficulty figuring out how to use the various frameworks and features as they are released. I don't want to discount the experience of anyone who has had difficulty however. Getting direct technical help may be the key to their sucess. I am a former Apple employee but this has given me no special privileges or advantages at all. Perhaps it has given me some particular skill at diving into header files to figure out a solution to a technical problem. The issue(s) I need the most help with revolve around generating revenues that don't involve advertising, subscriptions, dark patterns or racing to the bottom on pricing. The AppStore model makes it very difficult to use some of the techniques that worked in the old days of shrink wrap and direct online distribution; trial periods, version upgrades and other concepts that don't fit into the AppStore buy it once and get upgraded for life. It was my decision to make an application that incurred expensive development costs and it was also a risk to depend upon Apple and the AppStore. They sure do make it hard for small developers to try and make a living selling "professional" level applications.
- deleted 4y ago[deleted]
- cglong 4y ago> The issue(s) I need the most help with revolve around generating revenues that don't involve advertising, subscriptions, dark patterns or racing to the bottom on pricing. The AppStore model makes it very difficult to use some of the techniques that worked in the old days of shrink wrap and direct online distribution; trial periods, version upgrades and other concepts that don't fit into the AppStore buy it once and get upgraded for life. The part that bugs me is that Apple could fix these issues but is choosing not to. Rather than adding upgrade pricing (something developers have been asking for since 2009), they added and have been pushing for subscriptions :(
- chipotle_coyote 4y agoI’m not as down on subscriptions for apps as other people seem to be. If—and I recognize these are big “ifs” here—the annual price is reasonable (which I’d roughly define as “no more than what you’d be paying for upgrades if they were amortized over a yearly basis”), and developers use this stable recurring revenue to make frequent updates to their apps on a rolling release rather than holding big features back for major updates every one to three years, I’m happy enough to pay for them this way. Granted, I’d prefer to see the ability to handle subscriptions the way Panic does for their editor Nova, in which you get all the updates as long as your subscription is valid, and if you stop paying you stay on whatever the most recent version was when your subscription expires. (This is distinct from Jetbrains’ take on this, where when you stop paying you stay on the version that was current when your subscription started.) This is something I don’t think the App Store supports, either.
- princevegeta89 4y agoOne feedback I will provide: "Deprecate your shitty XCode IDE, and partner with Jetbrains. Give us a solid editor just like what Google did with Android Studio"
- fooker 4y agoXCode is amazing for working on large C++ codebases compared to pretty much everything else. The closest I have seen is QtCreator, but that's not as polished. The trendy ones don't even come close.
- squeaky-clean 4y agoHave you tried CLion? That or Visual Studio have been much better for C++ in my personal use cases at least.
- princevegeta89 4y ago+1 in my use cases as well, XCode was good for nothing. I was feeling punished whenever I had to do iOS development with XCode.
- fooker 4y agoYes, I have tried CLion, Visual Studio, and VSCode. Visual Studio is amazing for GUI debugging, and not much else. For large C++ codebases with some meta programming, these are all fairly bad at code completion and refactoring. VSCode is getting better though!
- BonoboIO 4y agoApple Support has left the chat
- jedberg 4y agoHow many people will start their conversation with "can you tell me why my app was rejected and how to fix it?"?
- sirsinsalot 4y agoWhy was my app taken off the store, and my developer account banned without explanation? No? No answer? Funny that.
- criddell 4y agoThey aren't going to answer you here.
- sirsinsalot 4y agoIt was rhetorical.
- view 4y agoThe App Review Guidelines at 4.3) Spam states: the App Store has enough ... dating apps. We will reject these apps unless they provide a unique, high-quality experience. Does the App Store accept any new dating apps at all? How high is the bar set for the definition of unique high-quality experience? I'd hate to invest time and money into creating an iOS app just to have it rejected. I'll try to ask this question on October 17th in the App Store Slack channel they've created but I'm just wondering what you all think here.
- crooked-v 4y agoMy guess is that this in response to the X,000,000 dating sites that are all owned by the same companies and are minimal rebrands with identical shared content in order to capture SEO clicks, and the inevitable webview wrapper dating apps for them.
- AtomicOrbital 4y agoAs a developer I avoid anything Apple ... their disjointed technical support forums are terrible ... if only they could clone stackexchange
- tkk23 4y agoInstead of cloning, they could just pay stackexchange to host it.
- h4waii 4y agoMaybe my app is too simple, but I have had no issues with developing for, submitting, and shipping downloads (with infrequent updates) in the Apple app store. Honestly, the major annoyance is paying $120/year while Google only charges a one-time $25, but it is what it is.
- fareesh 4y agoMy top complaints with Apple are - The documentation could be improved a lot - with examples ideally. - The App Review process seems to flag a number of the same issues which are subsequently resolved after sharing a video that there is already compliance. This could be improved - Showing specific error messages - I think this is somewhat Universal but Apple gets it wrong far more often. For example if you don't accept an Agreement somewhere in App Store Connect, you will just see a random error when you try to test In-App Purchase and some developers may think it's a problem with their code when in fact it's something else entirely. This wastes time and can be incredibly frustrating and demoralizing. Also the In-App _Purchase sandbox user flow is needlessly complicated.
- diego_moita 4y agoAnd also Xcode. And breaking existing functionality. But, in the end, it boils down to the fact that "developers, developers, developers" just isn't an Apple mantra (viz: Jobs' initial reluctance to open an appstore). They know that, as long as they corral a lot of paying customers the developers will keep coming, no matter how many problems they throw in the way.
- pjmlp 4y agoWhat about bringing back the "deprecated" documentation that is still quite relevant and only old timers like ourselves can find it, because we have the bookmarks and also know what to search for?
- busymom0 4y agoI recently went through the second one for my hacker news app HACK. I had an urgent bug fix update which fixed issues related to the hacker news website making some small html changes which broke the parsing code. Apple rejected the update saying my app didn’t allow user content to be flagged, blocked, hidden etc. this had already been dealt with in a prior update and my app already included these features. Somehow Apple reviewer decided to review the app without logging in and obviously without logging in, you won’t see the ability to flag, hide, block etc. This ended up wasting 2 days. And this is something which was already dealt with in prior update and my app already included.
- everyone 4y agoWill they answer questions like.. Why have I been waiting weeks for a review? Why was my app rejected? Why was my app taken down? I would imagine these would be like 99% of devs questions.
- PeterCorless 4y agoI remember when Apple first launched the System 7 Helpline. It was 13 May 1991. And it was the first time in Apple's history they took direct consumer questions. [I worked on the System 7 Helpline with the initial cadre of support reps.] At the time, they had some sort of developer support line which was considered practically a state secret. They didn't want anyone trying to reach Apple developers directly. Not even the people from the System 7 Helpline. I remember making a new version of the "System Errors DA" for System 7. Apple users considered me a god. The actual Apple developers were creatures from beyond time and space. Apple also only wanted to take limited calls from their dealer channel, and most of that was for hardware issues only. Supporting software at the developer level, unless you were at the Microsoft Office level, was anathema. So here we are thirty one years later and finally Apple is opening up a direct developer relations line. How might Apple's history have been altered had it actually been less standoffish towards developers in the 1990s, 2000s, and 2010s? Did I miss other iterations at something like this over the decades? [I have to admit it's been years since I've fallen off the Apple wagon other than as a user.] Also, why is this limited to mere "one-on-one 25-minute consultations?" Why can't it be a team Zoom call? Why can't it go for an hour? Where's the Slack channel? What would an annual team developer support agreement look like? (Scalable for individual developers, small teams, large teams, etc.) I guess this is a step in the right direction, but it still smacks of decades-ago thinking. Long overdue. But perhaps not sufficient for this day and age.
- nemothekid 4y ago>Also, why is this limited to mere "one-on-one 25-minute consultations?" Why can't it be a team Zoom call? Why can't it go for an hour? Where's the Slack channel? Aren't you a developer? How would you feel if your job was suddenly "customer support engineer" overnight? IMO, direct developer channels only makes sense when you are small; and one developer has the entire product in their head. Once the problem becomes large you end up with: 1. Developer knows nothing $problem, because it was written by a different team, effectively making them tier 3 support. 2. Developer quits because being "tier 3 support" wasn't communicated effectively in hiring. 3. Developer(s) actively avoid hour long team support sessions because developers aren't promoted on being closing support tickets, they are promoted on delivering features 4. Customer does not bring in enough revenue to support tying up $n developers for hours at a time. Not to say you cannot build great developer support systems; just that direct customer contact with the engineer who built $x isn't scalable.
- gtvwill 4y agoGonna ask the Devs if they thought about domestic violence and the ethical implications of their work whilst they coded a bunch of features and tech that enables it. Tracking through keytags, deleting messages, payment control. I'm gonna guess that one goes unanswered...
- apatheticonion 4y agoI wish I could write my native app in whatever language - say Rust - and use bindings for OS GUI libraries to render a UI. but it looks like Google and Apple require you to use Kotlin/Swift to create UIs
- cudgy 4y agoWhy? Kotlin and Swift are easy to learn and don’t require a special library and interop that needs to be updated with every new version of the SDK.
- apatheticonion 4y agoBecause it could facilitate more code sharing between the platforms, reducing development costs, increasing the talent pool of engineers who can contribute to native mobile projects, allow for development toolchains outside of XCode and Android Studio. It's just a case of offering a system API that could be called from whatever language - but Apple don't want iOS apps written in Kotlin or C++ and who knows why Android is so locked down.
- cudgy 4y agoFurther fragmentation to support many methods (eg languages and frameworks) to develop apps on a single platform also spreads the support of the platform thinner as there are fewer developers using a core set of methods on the platform, resulting in wasted and duplicated efforts across all the various methods. Your approach results in, for example, a developer familiar with a single or very few languages being able to develop across multiple domains using the same language regardless of whether it is appropriate for that domain. Basically, using only a hammer to build a house. Another approach that results in higher quality software is to have domain experts in each area using the languages and tools most optimized for that domain. Do you hire 20 Javascript developers doing all the programming across the entire solution? Or hire a mix of developers with different skillsets to achieve better quality? The hiring of only one type of developer is a lazy approach, in my opinion, and is largely responsible for poor quality of software with greater complexity.
- zackify 4y agoI tried “ask apple” It’s called using the forums. They reply once in a blue moon and never follow up on bugs.
- harry8 4y agoThe most appropriate question and one that will be scorned here, likely unasked there and even if it was no meaningful response offered is: "Why do you hate us so very, very much?"
- tcldr 4y agoI’m happy for the initiative – but only if it’s actually backed up with genuine resources. My fear is the typical ‘fanfare and forget’ approach. Plus I’m concerned that this format makes finding good answers to problems completely unsearchable. Lost in the focus on a 1-on-1 format. That seems unsustainable. I’d be happier if they gave proper resources to the existing dev forums. That means: Ditch the custom format, use discourse/stack exchange as the engine, but then actually answer questions and foster a community. It’s possible. Look at the Swift forums.