Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
orion-ix3549y@Jumpshot44 that produces some seriously messy code and nefarious memory leaks - don't think it'll help OP with his frustration
-
@orion-ix yeah I had read that in reviews but saw otherwise in some impressive apps. But maybe another solution other than Titanium might help.
-
I think that's just the plight of iOS dev. It's extremely limited and proprietary so you're forced to learn it from scratch. Not exactly appealing when you've already spent 4 years mastering cross platform languages like Java. Good luck, dude!
-
xroad23189yEx-Android dev here. Auto layout is your best friend, once you get the hang of it creating views will be a lot easier than on Android. If you want to set the constraints in code check out Cartography.
-
Scrappy779yI develop on Xcode as well as android studio, and I have to say, once you get used to Auto Layout and Xcode it is amazing and fluid. Android studio just feels behind its time, but the amount of flexibility android gives you vs iOS is amazing, so there's that too.
-
compatic799yAs an iOS Developer, user interface and interaction is so much more easy and fluid. Animating is a breeze in Obj-C. Data types are painless. And it automatically uses ARC.
-
@compatic (about ARC) which can be a pain, but is way less sloppy than calling System.gc().
as an Android dev of a few years, I HATE iOS. Coding on XCode vs Android Studio is a nightmare. The error logs are terrible in comparison to Java. Obj-C is a nightmare. Swift is cool, I'll admit, but I could probably build better interfaces that scale per device on an Etch-A-Sketch. Instead of creating a layout in Interface Builder that worked for all devices (freakin' impossible) I instead opted to save myself some time and get a reference of the constraints and adjust them PER DEVICE. If that's not shitty code practice, I don't know what is. when I code iOS apps I feel like I'm in college again, just doing whatever the hell I can to get a project done with. the problem with mobile dev is that, when you can, you want to target both OSes. typically I do Android first and switch to iOS. I probably should do iOS first and then work on the Android version
undefined