Apple sees no need to even justify these discrepancies, because this is what ultimate market power affords you. Apple's review literally said on the phone, when we raised these objections: "We are not going to talk about other apps". Abusive is case by case.
ΠΠΎΠΏΡΠΎΡ ΠΈ ΠΎΡΠ²Π΅Ρ: English 1. The App Store situation is still getting a lot of attention, so let’s start there. What workarounds did you and your team consider when Apple first refused to publish the update? How has the IAP dispute progressed now that the update is approved? What regulatory developments should we expect in the near future?
We’ve finally won a definitive right to exist in the App Store without paying the 30% fee or offering IAP. We had to offer a different free service, which I do not love, but so it goes. Apple is facing intense scrutiny in both the EU and US right now.
New EU regulations on App Stores launched: — All app removals must come with a 30-day notice, clear reasoning, and option to appeal. — Ranking in top charts must be transparent. — Reveal any differential treatment on sweetheart deals. — Plan term language.https://t.co/6HMhUNk28r
ΠΠΎΠΏΡΠΎΡ ΠΈ ΠΎΡΠ²Π΅Ρ: English 2. Do you believe that Apple’s pre-WWDC decision to overhaul the way they handle appeals is enough to level the playing field for smaller developers? Will products such as HEY finally get the chance to compete against the likes of Gmail (G Suite) and Netflix?
Absolutely not. It was a very small, almost token, step forward. But hopefully it’s the start of actually doing the work to level the playing field.
ΠΠΎΠΏΡΠΎΡ ΠΈ ΠΎΡΠ²Π΅Ρ: English 3. Has this publicity impacted the morale of your engineering team? It’s not every day that seemingly everyone is talking about your productβ¦ Could you tell me more about the engineering team? Does it in any way overlap with the team behind Basecamp? Are there people working on both products at once? Did you invite any of your former colleagues to work on HEY? How did you pick the initial members of this team and how did you approach expanding it?
It was a crushing first two weeks. Filled with anxiety and overwork. Not a happy time. I’m glad we’re past it now. It’s the same team that runs Basecamp. But now that HEY is a huge success we will be hiring quite a lot in the next few months. All postings appear on basecamp.com/jobs.
The last two weeks have felt like I've been playing a role in A FORTNIGHT IN THE LIFE OF A WORKAHOLIC. I'm ready to let the credits roll. I don't understand how people live like this for months. Or even years.
"The only reliable gauge Iβve found for future programmer success is looking at real code theyβve written, talking through bigger picture issues, and, if all that is swell, trying them out for size", https://t.co/i7Yc7Ghy8X
ΠΠΎΠΏΡΠΎΡ ΠΈ ΠΎΡΠ²Π΅Ρ: English 4. It is my understanding that HEY incorporates a greater number of native UI solutions compared to, say, Basecamp. Given the added complexity, has it been a challenge to keep development teams small? According to Sam Stephenson, you even built a library that generates native UI elements based on your web views’ HTML. Has this decision helped reduce the number of staff?
Yes, we will reveal all our new tech later this year. We worked hard to ensure that HEY could be built by a small team, and maintained too.
ΠΠΎΠΏΡΠΎΡ ΠΈ ΠΎΡΠ²Π΅Ρ: English 5. HEY’s focus on plain old HTML is surprising for a contemporary product. You stuck with server-side rendering while employing a number of tailor-made solutions to benefit from modern innovations. Are you keeping things βsimpleβ to make a statement about the standard-breaking practices of mainstream email providers?
We’re keeping things simpler because it works! It allows a small team to do so much more. Making a point that modern complexity is not necessary is a nice bonus, but it’s not the point. The point is to build a great product with a small team in a way where we can enjoy ourselves.
HEY is not just about making a better email service, it's about fighting for the very essence of email as a protocol, not a Google app. Monopolies have captured most of the internet, but email is still hanging in there… just barely. Now is the time to protect it!
ΠΠΎΠΏΡΠΎΡ ΠΈ ΠΎΡΠ²Π΅Ρ: English 6. Let’s talk about the recent controversy surrounding the email sharing feature. You promptly disabled it and promised to be more mindful of your services’ potential for abuse. What choices have you already made to ensure the security of your users’ data and what further actions are you planning on taking?
We hadn’t thought that public link feature through from the abuse angle. So we’re putting it back on the drawing board until we can do better. When something appears on hey.com, they have to be able to trust that it’s done right and with consent.
We've gotten many requests for HEY family plans. With a household of five, I totally get it. But family software is harder than it looks. Who owns the data? How do you protect against spouses spying? What about kids? If <13? And how to settle in a divorce? Have to get it right.
ΠΠΎΠΏΡΠΎΡ ΠΈ ΠΎΡΠ²Π΅Ρ: English 7. You often talk about the importance of having good written communication skills, particularly for developers. During the IAP crisis you proved yourself to be more than capable of standing your ground on Twitter. How did you organise the written exchange of ideas that led to the development of HEY? How did the product conceptually evolve over these two years? Are you happy with the results or should we expect big changes in the near future?
I’ve been writing for the web for 25 years. I keep practicing! And we’re a very writing-focused organization at Basecamp. Have been since the start. So all that came naturally. I think HEY’s core vision is incredibly strong, but of course we’ll expand and make things better.