You know what?

Young cocky React devs can suck my old fuckin LAMP and Objective-C balls.

Got a new freelance job and got brought in to triage a React Native iOS/Android app. Lead dev's first comment to me is: "Bro, have you ever used React Native".

To which I had to reply to save my honor publicly, "No, but I have like 8 years with Objective-C and 3 years with Swift, and 3 years with Node, so I maybe I'll still be able help. Sometimes it just helps to have a fresh set of eyes."

"Well, nobody but me can work on this code."

And that, as it turned out was almost true.

After going back and forth with our PM and this dev I finally get his code base.

"Just run "npm install" he says".

Like no fuckin shit junior... lets see if that will actually work.

Node 14... nope whole project dies.

Node 12 LTS... nope whole project dies.

Install all of react native globally because fuck it, try again... still dies.

Node 10 LTS... project installs but still won't run or build complaining about some conflict with React Native libraries and Cocoa pods.

Go back to my PM... "Um, this project won't work on any version of Node newer than about 5 years old... and even if it did it still won't build, and even if it would build it still runs like shit. And even if we fix all of that Apple might still tell us to fuck off because it's React Native.

Spend like a week in npm and node hell just trying to fucking hand install enough dependencies to unfuck this turds project.

All the while the original dev is still trying TO FIX HIS OWN FUCKING CODE while also being a cocky ass the entire time. Now, I can appreciate a cocky dev... I was horrendously cocky in my younger days and have only gotten marginally better with age. But if you're gonna be cocky, you also have to be good at it. And this guy was not.

Lo, we're not done. OG Dev comes down with "Corona Virus"... I put this in quotes because the dude ends up drawing out his "virus" for over 4 months before finally putting us in touch with "another dev team he sometimes uses".

Next, me and my PM get on a MS Teams call with this Indian house. No problems there, I've worked with the Indians before... but... these are guys are not good. They're talking about how they've already built the iOS build... but then I ask them what they did to sort out the ReactNative/Cocoa Pods conflict and they have no idea what I'm talking about.

Why?

Well, one of these suckers sends a link to some repo and I find out why. When he sends the link it exposes his email...

This Indian dude's emails was our-devs-name@gmail.com...

We'd been played.

Company sued the shit out of the OG dev and the Indian company he was selling off his work to.

I rewrote the app in Swift.

So, lets review... the React dev fucked up his own project so bad even he couldn't fix it... had to get a team of Indians to help who also couldn't fix it... was still a dickhead to me when I couldn't fix it... and in the end it was all so broken we had to just do a rewrite.

None of you get npm. None of you get React. None of you get that doing the web the way Mark Zucherberg does it just makes you a choad locked into that ecosystem. None of you can fix your own damn projects when one of the 6,000 dependency developers pushes breaking changes. None of you ever even bother with "npm audit fix" because if security was a concern you'd be using a server side language for fucking server side programming like a grown up.

So, next time a senior dev with 20 years exp. gets brought in to help triage a project that you yourself fucked up... Remember that the new thing you know and think makes you cool? It's not new and it's not cool. It's just JavaScript on the server so you script kiddies never have to learn anything but JavaScript... which makes you inarguably worse programmers.

And, MF, I was literally writing javascript while you were sucking your mommas titties so just chill... this shit ain't new and I've got a dozen of my own Node daemons running right now... difference is?

Mine are still working.

This is how I write my header signatures ;)

IOS SUCKS!! SWIFT SUCKS !! OBJECTIVE-C SUCKS!! SUCK MY DICK APPLE YOU PIECE OF SHIT !! Why did you have to make the language sooo counter intuitive, and so different from the popular languages you pain in the ass piece of shit, Why can't I throw exceptions from a constructor of a class?? Why do I have to use a fucking struct to just throw exceptions?? Can't class constructions fail you peice of shit?? huh? GOD DAMN IOS MAGGOT DEVELOPERS IF I EVER RUN INTO THOSE FUCKERS IM GONNA FUCKING RAPE EM BURN THEM ALIVE AND HAVE THEM FOR DINNER

Senior development manager in my org posted a rant in slack about how all our issues with app development are from

“Constantly moving goalposts from version to version of Xcode”

It took me a few minutes to calm myself down and not reply. So I’ll vent here to myself as a form of therapy instead.

Reality Check:
- You frequently discuss the fact that you don’t like following any of apples standards or app development guidelines. Bit rich to say the goalposts are moving when you have your back to them.

- We have a custom everything (navigation stack handler, table view like control etc). There’s nothing in these that can’t be done with the native ones. All that wasted dev time is on you guys.

- Last week a guy held a session about all the memory leaks he found in these custom libraries/controls. Again, your teams don’t know the basic fundamentals of the language or programming in general really. Not sure how that’s apples fault.

- Your “great emphasis on unit testing” has gotten us 21% coverage on iOS and an Android team recently said to us “yeah looks like the tests won’t compile. Well we haven’t touched them in like a year. Just ignore them”. Stability of the app is definitely on you and the team.

- Having half the app in react-native and half in native (split between objective-c and swift) is making nobodies life easier.

- The company forces us to use a custom built CI/CD solution that regularly runs out of memory, reports false negatives and has no specific mobile features built in. Did apple force this on us too?

- Shut the fuck up

Windows vs Mac vs Linux
Swift vs Objective-C
Emacs vs Vim
GPL vs Apache License vs MIT license
Android vs iOS vs Windows phone*
Skype vs Facetime
GIF vs GIF
Peppermint vs Spearmint**
Men vs Women
I DON'T GIVE A FUCK!
IM HAPPY WITH WHAT I HAVE, SO STOP PREACHING OR I'LL STAB YOU!

Ok? 😑

Went to hackathon @ Google HQ in NYC. Gotta say it was pretty shitty. Most people are JavaScript nerds and some code in objective-C, xcode (4-5 out of 50). The rest are chemists, scientists and general folks. Not what I anticipated when you know it's more like iOS hackathon. Anyways it was good to see the shittiest demos in my life made in less than 12 hours. We had 4.5 people working on a toilet project called "I gotta go". Public bathroom locator... One guy coded in JS, xcode and react Native. Another dude was pushing all the code to GitHub and doing backend in firebase. The third guy was making a website for no reason and then I see it's hosted weebly. He hand coded first, I looked what he is doing - just HTML tags. Thank God some organizers helped us and we had a 4 click demo with basic text and no real functionality. Plus the website who never seen. What a fucking waste of $100 and two days.

Still looking for jobs and look what I found:

Title starts off bad, they can't even spell Android LOL, then go on to ask for someone with experience with Xcode and objective-c, interface builder and basically iOS.

How are these people able to create job listings without any actual research?

Thought I'd add the last line of my similar rant,

Lol What a fucking joke...

I'm still at my first job, got the job by word of mouth from a friend.

This company wants me to develop both their iOS and Android apps, and being the solo developer it's a long process. I forgot to mention I had to learn objective-c on the job, and being from a java background Android was easy to pick up but it wasn't exactly 100% easy either.

8 months down the line I finished the iOS app and working on the Android app, which is more so copying the features I did with the Android prototype I worked on at the start.

I get paid minimum wage with from the looks of it no sight of a pay raise.

This company doesn't seem to know about how difficult it is to be the only developer for two apps in two different languages.

Anyway aside from this I was wondering if I could get some advice, I want to apply for jobs while I finish up the Android app, but is it a good idea to put the company I work for on my CV? I don't want to risk getting found out for looking for a job, without my boss knowing.

Would it be ideal to just have some sort of more information on request type thing if the jobs I apply for respond?

I guess I could stay until I'm here for one year (student advisor said this) but in saying that I don't think he understands that software development is done in projects rather than time, and after these apps I'll have to start on a new app from scratch, which I'm not looking forward to.

Anyways for any advice you guys give me thanks in advance I really appreciate any input, just wanna get out of this job, the 10 hours of commute I spend a week is killing me :/ along with it being expensive.

Did I ever tell you kids about the time I worked for a company that got a contract to develop an iOS application around some object detection software that had been developed by another team?

Company I was working for was a tiny software consultancy, and this was my first ever dev job (I’m at my second now 😅). Nobody at the company has experience building mobile applications but CEO decides that the app should be written in React Native because _he_ knows React Native.

During a meeting with the client, CEO jokes about how easy the ask is and says he could finish it in a weekend. Please note that Head of Engineering had already budgeted a quarter for the work. CEO says we can do it in a week! And moves up the deadline. And only assigns two engineers to project. I am not one of those engineers.

The two engineers that are put on it struggle. A lot. They can’t seem to get the object detection to work at all, and the code that’s already written is in Objective-C. I realize one of the issues is that the engineers on the project can’t read Objective-C because they have no experience with Objective-C or even C. I have experience with C, so I volunteer to take a look at it to try to see what’s going on.

Turns out the problem is that the models are trained on one type of image format and the iPhone camera takes images in a different format.

The end of the week comes, they do not succeed in figuring out the image conversion in React Native. There’s an in-person demo with the customers scheduled for the next Monday. CEO spends the weekend trying to build the app. Only succeeds in locking literally every other engineer out of the project.

They manage to negotiate a second chance where we deliver what we were supposed to deliver at the original schedule.

I spent the weekend looking up how to convert images and figure it would be a lot easier to interface with the Objective-C if we used Swift. Taught myself enough Swift over the weekend to feel dangerous. Spoke to Head of Engineering on Monday and proposed solution — start over in Swift. Volunteer to lead effort. Eventually convince them it’s a good idea (and really, what’s the worst that can happen? If this solves our main problem at the moment, that’s still more progress than the original team made)

Spend the next week working 16 hour days building out application. Meet requirements for next deadline. Save contract.

And that’s ONE of the stories of my first dev job that got me hired as a senior engineer despite only having 10 months of work experience in the industry.

Idiot people...
Today someone asked me how long I programmed for iOS, Told him I started really mastering iOS development since Swift was released, as I didn’t really focus on Objective C. He told me if I need any help, just ask him as he develops for iOS since two decenia... He calls himself a Senior web developer. First of all what has web development to do with iOS? And how the f*** can he program for iOS if it didn’t exist at that time.
It’s not because I’m a student I’m that thumb...
learnt the lesson not to believe everything everyone sais.

I had been working on a side project iOS app for years using Objective-C, then Swift came out and I started rewriting the whole thing in Swift and continued working on it for months... Few days ago while I was just playing with react-native I accidentally finished the whole thing in a few hours... Feel kinda stupid for wasting all those years

I'm working at this company where I have to update their app both for Android and iOS and it was originally coded by what seems to be one guy, that has written some of the worse code I've seen (I've seen pretty bad code when I was at uni), there is so much uncommented code, commented code with no real reason on why it's commented, variables that are one or two letters, Lots and Lots of magical numbers for things like images! And for the first few weeks working on the iOS app I was also still learning objective-c and had to look at his code for reference, I cringed so much.

I take pride in my commented code, I take pride in writing description for methods and having my variables at the top of a class and explain exactly why it's a constant. I'm also only just a recent graduate.

This guy that worked out this app is a senior developer, now working on security software for a bank, how is he even allowed to code?

Xcode, the most piece of shit motherfucking IDE!!!

iOS dev here
Just wanted to share my experience on updating Xcode and why I schedule 3 hours for this process.
So, updating Xcode via the AppStore has always been flaky at best and ofcouse Xcode needs to be closed first. You hit update, the button turns gray, half an hour in you still see no progress...
That's why I often just download it from the dev center. But since Xcode Ghost the app is also wrapped in a signed container.
So,
Downloading: 10 minutes
Expaning: 60 minutes!!!
After that I move the app in place and fire it up, always have to close my music player first grrr...
After that Gate Keeper verifies the app for another 60 minutes.
Finally Xcode comes to live.
Only need to install new command line tools for another few minutes and I can continue coding.
Wait. Half my day is over!
Why Apple? Why?
#wk24

Area of focus: Native iOS dev

Why: Spent years trying hybrid tools, dealing with the most ridiculous errors, bugs and issues you can begin to comprehend and then ... something magical happened. I got a book on Objective-c, learned a little, tried a simple app ... and it worked ... like properly worked, and on all the devices without taking half the RAM.

I'll say that again as I don't think it landed. In Objective-c, I got no issues where only the CEO's phone + OS version meant I couldn't load a map and a pin (looking at you titanium!!!)

In Objective-c, I wasn't promised storyboards and autolayout, only to find out they are completely different, and may god help you trying to google the issues, as the only ones to show up would be the native tools (looking at you Xamarin)

In Objective-c, my app doesn't instantly consume 125mb of RAM to load a fucking webview (looking at you ... well nearly every other hybrid tool)

... it just works. Then Swift came along and things only got better.

I’m a long time Objective-C and Swift developer...I’ve been asked to “research” a project using React Native.

It felt dirty to be writing an iOS app using JavaScript.

I’m still not sure why and how React Native is better/faster than native Swift.

Someone change my mind...

Youtube's API docs for iOS is still in Objective-C.

Having to use Xcode 4 alongside the new 8 to support old iOS versions. I almost wrote the code twice, once in Swift and once in Obj-C.

"Have you tried regenerating your provisioning profiles?" Say it one more time mothefucker I dare you I double fucking dare you.

Anybody here who does mobile development(Android or IOS) (not Windows) without using native languages like Java, Swift or objective-C and is able to get the performance like of those on heavy resource using apps?

Be me
Work at software contracting company
Get a new client, iOS objective-c app with ~40000 lines of code
Previous Dev didn't leave a single comment, and he didn't use a database, he used 'NSUserDefaults'

It drives me Insane that AWS still doesn't support Swift 3 for iOS. We're almost to the point where Apple is going to drop Swift 2 support in XCode and Amazon STILL has not gotten it.

I've started deploying Gateway APIs in Objective-C and linking them to the bridging header just so we can finally move foreword in our company and quit relying on legacy Swift support. Which is something I was really trying to avoid because we don't like mixing languages unless absolutely necessary. It's not a problem, but it's incredibly annoying to me. What IS a problem is having to start new projects already using legacy code from the very beginning.

What is amazon going to do when the next release of XCode comes out? Tell all new customers to downgrade?

Why even offer native Swift APIs if you're going to go this long and still not migrate, Amazon?!

I sexually identify as Objective-C

I actually would love to write everything in objective c
Even my node/react applications

Swift SUCKS

Why?
Because of its absolutely useless complexity...
a total simple thing: i have a string and want to concat a integer with it, so:
var x = stringVar + intVar; right? NO
its var x = stringVar + String(intVar);
or getting the index of a element in a array?
var index = array.indexOf(element); thats logic, right??? Not for swift, gotta go with: var index = array.index(of: element); WTF??!!
And all the other shit: nil instead of null, int++? Nope.
And there are SO MANY MORE things, where u just think, Apple really though different........than all normal coding languages.......

I´ll honestly rather learn C and recode Ios or have a look at objective-c...

I'm sending you the codebase now, but don't open it in anything above Xcode 4 or else it breaks

> make
HEY
YOU NEED AN }
YOU NEED A ;
YOU NEED AN @END
YOU PUT A VOID IN A UNARY THINGY
make errors: 4
>
fix typo
> make
Compiled successfully.
>

sanctuaryGuardian();

When engineers get so CS-driven they can’t see simple things 🙃

Another manager messaged me and my boss last night to ask whether he’ll have to expose a certain function to be available in objective c classes (we’re iOS devs and most of our code is in swift, but some older stuff is still in .m files). He said he dug into the lower level code and didn’t see any connections or exposures so he assumes he’ll have to add these. My boss concurred and told him to go ahead and make them available.

Then I showed up with my didn’t go to university brain & searched the codebase for calls to that function from .m classes. There were like a hundred lol, working just fine. It’s already exposed. Neither of them thought to do that.

So frustrating to learn Swift when I already know objective-c. It's like I know what I'm doing, but really, I don't

what the fuck I can't edit the rant after 5 minutes I am fucking posting a new rant which have that last rant ...Why they update the fucking x code in every fucking 15 days . Well some libraries are deprecated oh cool I can use my shit as an object. And why third party libraries don't provide some good documentation of their sdk's . What the fuck is that and I will personally kill auto layout by entering in the mac myself. What is the use of that fucking debugging tool if I know don't the crap of my code that in which class I have done something terribly wrong what the fuck . Oh cool I am having that clang error and I don't know how to wipe my ass. And please fucking don't tell me to use xib code in xcode for my project if there will be 600 screens I will still fucking use storyboard for that. I don't fuck with xib files do you hear me. And fucking stackoverflow ..what the fuck is wrong if I forget an single comma during posting a question ..what the fuck..and you know what the real feeling is when I post a issue on stackoverflow and I got nothing from them expect some minus points...and then the holy fucking coder inside me tells me to solve that fucking problem and I feel like having dope bitch. FUCCKKKK..

The awkward moment when you name your dictionary "dic" and realize that while explaining a piece of code to a female colleague. 😳

"Our app needs a barcode scanner"
Fair enough, let's do this!
Android implementation using Zxing: 3 days. Ios: 9 days...
1. Dev iPhone has a subtle hw defect that doesn't let it connect to the computer anymore...
2. Our app-framework doesn't have a proper plugin for ios barcode scanners yet.
3. The first barcodescanner implementation is completely broken
4. Swift is not possible because of conflicting framework plugins
5. Build a plugin from scratch, using zxing objective c port.
6. Build problems with main app.
7. Fuck my life

I bonded a lot with a co-worker over the last several months as I had to mentor him in iOS and how to maintain our apps. We mostly bonded over how much we hate Objective-C and the management of the project. Now we are buying Christmas presents for eachother. Bad code brings people together

NSLog(someStrVar);
Instead of
NSLog(@“%@“, someStrVar);

Wow. All these weekly rants work so well with my current project lol.
A 4-5 year old iOS project, written in Objective-C with some jQuery thrown in to keep things interesting. Its the kind of codebase where you look at some code and think "what the....how....you know what nevermind". Everything has CoreData mangled into it somewhere which causes all kinds of issues. got search results from a web API? better save those to CoreData. Why? Who knows...

I often wonder why JS is the only language that has the native support from browsers and native built in DOM apis?
The world has come up to a saturation point for so many techs:
- if a software is needed to be created for mobile, it must go through 1 layer of java (aka JVM) or objective C (i guess? for ios) before being understood by the CPU

- if a software is needed to be run via browser( which itself is made to run on jvm, objective c or machine language), it must go through one layer of js interpretters before being understood by the CPU

all the OS are made on C but the application and application platforms are made on specific languages. I wonder why can't there be a single application platform, if all of them(browser, JVM,objective C and whatever .exe apps run on) are doing the same thing and are equally mature to handle every usecase?

It all started when I got my first iPhone. I had so many ideas for any kinds of apps, so I wanted to learn how to program them. I went to school and learnt programming. (I started with Java)
While beeing at that school I taught myself Objective-C and I started to write Apps. After school I got a job as an iOS Developer.

I wonder the creator of jQuery , Objective C , Erlang, what were they smoking while creating these programming languages......

Whenever I code in Erlang (server side) or Objective C (iOS) I can feel that the creator is damn high...

Objective C is weird that I have to call an object by allocation . Like get me thinking is that OOP? Or Functional.

I've just started learning Objective-C and Cocoa Touch so I can make iOS apps.

I reckon this "mobile" thing has got legs. I want to get in there on the ground floor with app development before everyone's at it.

iOS development: When Google didn't realise that you trying to start a serious development question dealing with the keyword "swift" and anoying Taylor Swift searchRequestBombs it. Anytime.

Hey Google come on, I'm interested in serious answers and not that kind of celeb rubbish bullshit 😡

And what the hell about Kim Kardashian ist that your kind of interpretation of objective-c or?

Just so you guys know, coding with react-native will most likely implicate to write some objective-c, because react-native on its own wasn’t crappy enough.
Gimme a rope please

[POLL]: What do you prefer making iOS apps?

- Swift
- Objective-C

I'm trying to go into iOS app development. Should I bother with Objective-C or is Swift the new way to go?

Hello everyone, looking for some career advice here.

First of let me list my credentials off here. I graduated in 2016 with a BS in Computer Science. While I was working on my degree I worked as an engineering for 3 years in a cell phone repair company. What this entailed was managing/reverse engineering a software solution of one of that companies vendors, writing documentation etc (it started as a summer internship and became a job that I worked full time over Summers and up to 30/week in the school year).

Anyway, the vendor I acted as a point of contact offered me a job before I graduated and I started with them in May 2016 as a junior most Dev. Since then I have have maintained the same job tittle (software developer), however my duties have increased.

Currently I maintain several of our build servers, manage software releases (as in I am the lead developer of this application) for the service that makes 90% of this companies money, and am the subject matter expert for everything regarding smartphone diagnostics. I've literally been entrusted with access to all of the company servers for if something goes wrong. I'm also training our newest developers and being told I'm doing a good job at doing so.

Currently with my job on a day to day basis I'm working with Java, Android, C++, Golang, MongoDB, iOS in Objective C, and Python

(Please note this is a small company of less than 50 people)

Currently I'm only being paid 60k USD and am wondering if I should hold out for a raise or consider looking for a better job? ( Please note I live in the east coast in an area where the cost of living isn't absurd).
Because this job was practically handed to me I don't know what to expect and feel imposter syndrome as I think I deserve better pay but think I don't have enough years experience. All advice is welcome

Worked as a swift ios developer for 2years now, boycotted java (android) and objective-c alltogether.
Have to do both plus javascript because my cto is marvelled by the promises of react-native...
The damn guy doesn’t have to implement a single line of code ! I do !
As if having to dev on xcode 9 wasn’t bad enough already 👏👏

Sending you the Xcode project now...

Non-ARC

swift protocol extensions > objective-c categories

Why is iOS debugging so fucking useless? Instead of having a normal stack trace which takes you to the line of code that went wrong it just takes you to the bootstrap line in AppDelegate with a random code and basically says "Fuck you, figure it out yourself". Their stack traces are just as useless. IS THIS WHAT SOME PEOPLE CALL THE PREMIERE DEVELOPMENT EXPERIENCE, GODDAMNIT? at least Swift is nice tho, unlike Objective-C

Took me two hours to realize this. I guess I will spend a lifetime to accept it.

Quick question to you guys and gals,

I really want to become an iOS app developer. I know it would be long and painful way to learn Objective-C (some say it looks like alien language compared to C). Swift is rather new, much easier to learn, but I know Objective-C is a must to be considered as true iOS dev.

The question is: is there such a need of iOS developers (I mean UK/Canada/US/Germany)?. I live in Poland and there's not much to do in iOS development (few job offers, everybody is hyped by JS and frameworks changing every year, some offers are often underpayed remote work for foreign clients). I am now 20 years old, still learning at Uni and not having any responsibilities, so I may go someday to UK for a year or two, since the market for iOS devs is more diversed and bigger than in Poland. I know I am complaining (most Poles do that), but I've learned English since I was 4 and it's a pity not to use it as a resource to get a better job offer than in my mother country.

Thanks for all the responses, especially from people working as iOS devs

coming back to objective-c after half a year coding in swift and forgetting about semicolons everywhere

I know android java, kotlin.. So for iOs development what should I learn?
1.Flutter
2.React native
3.Swift
4.Objective C

Which and why?
I would prefer the one with lowest learning curve.

For Apple hardware, including iPhone, iPad, and iPod Touch, iOS app development is the most common way of making mobile applications . The software is written in the Swift programming language or Objective-C and then submitted to the App Store for users to download.

In case you're a mobile application developer, you might have had second thoughts about iOS improvement. Every designer needs a Mac PC— Macs are more costly than their Windows-based partners. Moreover, when you complete your application, it faces a tough quality survey measure before it gets circulated through the App Store.

Most of my previous experience is in Java but my current area of focus is iOS apps for healthcare. Patient casenote management system and an electronic form solution for paramedics in ambulances. Im currently using both Java and Swift for my dissertation, an iOS app with a Java backend using Dropwizard for REST. iOS can be good but Im eager to get away from Objective-C. I wouldnt mind going back to java full time or even maybe C# since they are basically the same thing.

Recently asked myself questions:
Which is the most unpleasant when you developing a mobile application (for me its when design(UI/UX) changes after feature was developed.
which is the most complicated stage in developing a mobile application for you
Place plus(like) if you are mobile dev
P.S. Unicorns are real🦄🦄🦄

Getting started with my dissertation project for my degree. Using Java and Dropwizard for a backend service with a nice iOS client in Swift. Will make such a refreshing change from hacking crappy eForms together with jQuery and an Objective-C native bridge.

So........ My employer want me and another senior to complete 2 mobile applications on Qualcomm's CSRMESH both in Android (Java) and iOS (must use objective-c) to complete in 3 months time with 198 complex functionality. Some of them are hidden features(employer want us to find out our self) (this app is from Hong Kong)

The problem is , the library is shit and the sample code is messy. CSR still use Grade 2.1.1 for the project. Boss want us a new UI for the app, I should not code it but design it first in figma, because boss keep changing things from second to second.

I'm no iOS developer, so sorry if this is a stupid question. I was told a particular app I'm looking to make an Android version for was built in objective-C and uses Ruby and AWS for the backend. so presumably I'd need to plug into AWS for my app,im just not sure how Ruby fits in...

is there any need to learn objective c for ios app development if we are already planning to switch to swift language.. ?

After more 3 years developing for the web I’m considering to learn Swift and Objective-C and then switch to iOS hoping to find a job which involves less multitasking (now I’m split between front-end, back-end, DevOps and other), what’s do you think about a switch like this?

You know what's worse than getting an exception figuring out after wasting few hours, cleaning your project would solve it. Thank you Xcode ;(