Either you get a $75 iPhone SE or you have something for free with your MacBook. Anyone with a computer still wants to use a hardware Android device for any serious testing. And then there's the differences between all of the builds between the brands. I bet you want to test on a Xiaomi before you want to declare that push notifications work.
Yes, this is the expensive part. Obviously if you are developing for iOS or porting an iOS app then you need the hardware. But it seems like an unusually high barrier for implementing a "sign in with" button.
As soon as you're going to be involved in designing or building back-end API's and features that cross a lot of layers not being able to run applications from Xcode and Android Studio and understanding the other platform no matter if you're an iOS developer or Android developer limits your career.
I need at least to see what my Android developer did for me before I can accept his or her work. That's what happens when you go up the ladder. That's why I have the full toolchain on my computer and obviously bought an Android phone.
So it makes sense that for you, spending $0 to test on Android makes sense, but on the flip side, Apple has intentionally engineered their developer program to have a four figure entrance fee, and frankly most indie developers can't shell out potentially several thousand dollars on OSX/iOS devices and licenses just to do some testing, especially when as the developer above said, "they can ask a friend to test".
Sounds like these so-called “indie devs” who cannot afford to build for iOS devices should not tackle projects/clients that require building for iOS. Or, if a client is in the mix, bill the client a large enough fee to cover the cost of testing on real devices. That’s not a problem Apple is responsible for solving.
I would never rely on developing, testing, and releasing an Android app on a simulator alone. I don’t want to buy a bunch of Android devices. So I don’t take on work that is meant for Android, or I hire people who can properly test on devices. Pretty simple—and it’s both my choice and a matter of professional responsibility and accountability to ship work I can stand behind.
Apple isn’t going to change any time soon. I’m so tired of the disingenuous moaning from “indie devs” who want to take on projects for and make money from iOS, but can’t be bothered to get over their own personal anti-Apple feelings to buy a device.
The ecosystem of Apple devices are hardware and software. The simulators and build tools are never enough. You wouldn’t ship an app for Apple Watch without testing it on a watch, would you? Or would you ship it relying only on having one friend with an Apple Watch test it? Sounds lazy and unprofessional—and if an indie dev can’t do the job right, they shouldn’t take on the job.
That razor cuts both ways, and I'd point out that this situation is very similar to how OSX comes with Windows bootcamp, but a Windows 10 machine can't run OSX. If you run OSX, running Windows is something that you might just have to do. But if you're a Windows user, outside of walled garden development, there's not much point to OSX
While Android may make up the majority of devices worldwide, Apple devices are still very popular among wealthy clients (anyone living in the west would meet this criteria), which is ultimately the part of population business care about most.
Simply put, supporting Apple devices is very profitable. No company is going to leave money on the table due to niche ideological concerns.
https://www.statista.com/statistics/266572/market-share-held... https://gs.statcounter.com/os-market-share/mobile/united-sta...
That's nice if the only thing you do is selling eyeballs with adware. If you're actually looking to make money in sales you'd be a fool to not support iOS. I'd call it an obligation to your wallet.
My first MacBook (used for Xcode that is) costed 250 dollar coupled with a 200 dollar iPad 2 around 2013-2014. The iPad 2 was stolen and the MacBook 2008 kept working until around 2018 but was replaced in 2015.
But the grandparent simply needed to test a login feature that required iCloud. Any iPhone would do.
A new one, sure. You could buy a 2012 MBP on Craigslist for $200, and a refurbished iPhone 6 for $50 or less.
If you're going to be a mobile developer, supporting the android 80% is far cheaper and easier than supporting the iOS 20%. It then shouldn't be a surprise if the 80% get better support than the 20%.
Of course you do: Please implement this iOS application/feature in Android.
Not being able to run an application from Xcode onto an iOS device severely hampers your career. I have to deal with so many Android developers and their output I absolutely cannot afford the luxury to not run Android apps from Android Studio.
I don't think Sign In With Apple will be a huge hit on Android anyway. But perhaps you could share your code on Github for people that run into the same requirements?