4 ms·
I 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
by PeterCorless 4y ago
I 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.