4 ms·
I work in both too and will take Xcode any day of the week over AS. It has plenty of downsides but it's fast and surfaces errors well. YMMV.
by jurip 2y ago
I work in both too and will take Xcode any day of the week over AS. It has plenty of downsides but it's fast and surfaces errors well. YMMV.
- tartuffe78 2y agoAgreed, every time I open AS to update my company's Android apps (infrequently) I have to spend an hour Googling odd Java memory errors and grade sync complaints before I can do the minor tweaks I need to do to the actual app.
- lawgimenez 2y agoSounds to me that your Android codebase is a Frankenstein of a codebase.
- jwells89 2y agoAlso prefer Xcode. As long as you stay away from XIBs and Storyboards it’s more responsive than Android Studio. And yeah, if you let a project lapse on gradle and library updates for any length of time at all be prepared for a fight to get it all brought back up to speed. Swift Package Manager is generally less of a headache. Some of AS’ “smart” features are also more of a hindrance than a help at times, and don’t even get me started on ProGuard (which has no Apple ecosystem equivalent).
- iosguyryan 2y agoAlso. That said, autocomplete outside of Xcode is way more accurate. The latest beta predictive code is even worse than what we had… hallucinates APIs for the most vanilla of Foundation calls. Half my reflexive autocompletes now turn into — wtf I accepted this junk AI idea?