Earlier quoted context omitted.
Apple is notoriously bureaucratic. So its not surprising that innovation is stifled. I really hate this duality b/w innovation and stability... perhaps if more startups were focused on longer term survivability, it would be better for society overall?
I wonder if Apple's satellite operations (like the Siri team in Ottawa, Canada, for example) might have some autonomy and self direction simply due to distance from the mothership. As for a shift in startup culture, what is more tempting than 5 to 10 years of hard work into billion dollar exits? Local governments could start offering tax incentives that build over time—or more aggressively, have steep disincentives o…
Apple acquires Buddybuild
111–120 of 170 posts
Re: Apple acquires Buddybuild
#112I'm happy for the founders, this is probably a good and profitable exit for them. But as a customer I am really sad and disappointed. Apple has a very bad reputation when it comes to taking over products like this. TestFlight is the prime example. TestFlight basically disappeared for a year until coming back as a more limited and slower Apple branded service. And by slow I mostly mean, it takes 6 months for bugs to b…
Apple is notoriously bureaucratic. So its not surprising that innovation is stifled. I really hate this duality b/w innovation and stability... perhaps if more startups were focused on longer term survivability, it would be better for society overall?
Re: Apple acquires Buddybuild
#113I'm happy for the founders, this is probably a good and profitable exit for them. But as a customer I am really sad and disappointed. Apple has a very bad reputation when it comes to taking over products like this. TestFlight is the prime example. TestFlight basically disappeared for a year until coming back as a more limited and slower Apple branded service. And by slow I mostly mean, it takes 6 months for bugs to b…
Sometimes I wonder - isn't that an opportunity in disguise for another shop to fill the gaps? Or I am missing something?
Re: Apple acquires Buddybuild
#114Re: Apple acquires Buddybuild
#115Earlier quoted context omitted.
This may have been historically true, but our internal data shows us that starting early 2017, people in tier 1 countries were equally likely to pay and have comparable LTV on both platforms. And if you also going to launch in EU/Australia/Canada, you will have a nearly 50-50 split of ios and android users on a platform neutral app. So the classical logic of implementing on iOS first doesn't really apply anymore. Now…
The logic still applies. 1. Start with platform you're most comfortable with. 2. Iterate on product until you have a winning formula 3. Replicate on 2nd platform to double revenues Building is a lot easier than identifying what to build, better to speedily experiment on one platform.
Re: Apple acquires Buddybuild
#116Apple needs to drastically simplify how Xcode builds work instead of acquiring more companies. For example, provisioning profiles solve a problem that doesn't exist while creating a dozen more. Xcode is still limited to macOS. On the deployment side iTunes Connect is possibly the worst website that I've used. It's incredibly slow (both the front and backend) and has limited options for phased releases.
Yes, their IDE was made for their platform. I'm not seeing why this is a problem.
Re: Apple acquires Buddybuild
#117Earlier quoted context omitted.
I wonder if Apple's satellite operations (like the Siri team in Ottawa, Canada, for example) might have some autonomy and self direction simply due to distance from the mothership. As for a shift in startup culture, what is more tempting than 5 to 10 years of hard work into billion dollar exits? Local governments could start offering tax incentives that build over time—or more aggressively, have steep disincentives o…
Siri team in Ottawa? I find that hard to believe. Why would such an important team not be on the main campus?
Re: Apple acquires Buddybuild
#118Apple needs to drastically simplify how Xcode builds work instead of acquiring more companies. For example, provisioning profiles solve a problem that doesn't exist while creating a dozen more. Xcode is still limited to macOS. On the deployment side iTunes Connect is possibly the worst website that I've used. It's incredibly slow (both the front and backend) and has limited options for phased releases.
"Xcode is still limited to macOS." Yes, their IDE was made for their platform. I'm not seeing why this is a problem.
Re: Apple acquires Buddybuild
#119Re: Apple acquires Buddybuild
#120Earlier quoted context omitted.
The logic still applies. 1. Start with platform you're most comfortable with. 2. Iterate on product until you have a winning formula 3. Replicate on 2nd platform to double revenues Building is a lot easier than identifying what to build, better to speedily experiment on one platform.
In my opinion the new logic is build in React Native (unless your app fits in the 10% of use cases that won't work well with RN), then deploy to both at once. We have had excellent results.
Tbh, I'm not sure how many use cases don't fit either React Native or Unity, I'd practically never choose to do an app another way these days.