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
-
@Kaji been the opposite? You've had an objective-c app take 125mb+ RAM and a hybrid not???
I call that a 40cm problem ... the problem sits 40cm away from the computer -
You are correct. It just works. For one platform, that is.
Imagine now companies that don't want to pay for iOS developers, don't want to have the experts for any platform. Why? Because there are a lot of mobile platforms. And you can have a hybrid / xamarin developer who knows its job and not necessarily all about aaaaall the mobile platforms the application is about, but knows only the necessary to make it.
With hybrid apps and with xamarin apps, this is a reality. With native, this is a no-no. You have to learn the platform from the ground up. Period.
If companies tried at least to teach their developers what is needed, then probably you would have all the right of the world. But the answer is no. They don't. They won't. Well, not the majority anyways.
So, I want a multiplatform app and have, let's say 2 developers. I wouldn't decide if I was one of them to go native. It's a death trap, I tell you.
But! You can always do it your way. eg. xamarin for code and Xcode for layout. -
@practiseSafeHex Nonono, opposite as in I've never been able to find something that makes sense of how to get started with iOS (see my first rant).
That said, no denying the other issue could be a factor there as well, however. -
@pkats code with Xamarin and layout with Xcode? I'd sooner try mow my lawn with an electric toothbrush.
Most big companies are building native as they see the advantages. It's generally startups with no cash that opt for hybrid, and it's often the first thing that gets replaced when they land some investment. That's what I've been doing.
I've had no problem finding work being a primarily iOS dev. -
@practiseSafeHex as for the startups use of hubrid and such, yes. Just yes. One thing that they like I think is the following "hey, I see you work with C# in that multiplatform mobile app. Why don't I set you up for a new project in asp.net?"
True story btw.
Starting with native means to start knowing the platform from the ground up. But how? The documentation is not always there for you. Sometimes you need to pay for better. These startups (and me) don't have the money or they don't want to pay for documentation. It would be good if your company wanted to teach you the better way to develop applications...
I think it's best to start with something you are familiar with. You don't have to learn all the platform sir starters. You need a jump start. A boost!
As for xamarin and Xcode, what would you say if I told you that you can have the same layout and outlet, custom views and stuff only with C#? I don't say go for it, I just say there is a way. I have walked it. -
@pkats you don't need companies to pay for anything. I bought a €30 book on objective-c and read it over a few weekends, and that was enough. Now apple have a free swift book and playground apps and tutorials out the ying yang. There is no excuse for not being able to learn.
As for learning all the features of the platform first ... yes you absolutely do. When I hire a junior dev, day one I sit them down, give them links to in depth tutorials. They are not allowed to touch real code until I see them completed.
I have been bitten so many times from "senior" devs and "lead" designers who think that just because they can make or design a blue nav bar that they are professionals.
You won't get anywhere in life cutting corners. -
@practiseSafeHex I agree but only if you have the time. If you have to compromise, especially if you don't have the time for the alternative, you are bound to start with knowing of the essentials from a platform. I know it's not quite good but it's a reality nonetheless.
But that wasn't the point I wanted to mention. The point was that you start with the most familiar of them all. That way you can jump start your project, you have acquired the boost and you are already half the way.
So hybrid may be better for web developers, xamarin for Windows and Java-like programmers, native for dedicated ones that want to learn all there is. -
@practiseSafeHex How profitable is it to be a ios dev in your country? I am planning to go to the UK right after getting Bachelors at University, Juniors with little experience in Poland (Max 1 year) gets around 800-1200$ per month do I think it's crappy pay
-
@peterzig well you can fairly easily check that. Go to job board websites and recruiter pages to see what they offer.
I would say it's not easy to find one with zero experience. Only place that would do that is a huge company looking for an intern. Typically they would pay less because they will be giving you time to learn.
I'm not based in the U.K., so can't give you figures -
There is a new kid on the native block. It interprets json like html and outputs a native android and ios app.
www.jasonette.com -
@heyheni can't believe it. In a past company I worked with someone who proposed the same idea. Wonder was it built by him?
It was a horrific idea back then and still feel the same now, for so many reasons.
Not only does this entire JSON parser need to loaded into memory, but you also have to work with strings for everything, which is always a nightmare, and don't get me started on the security issues.
If people spent as much time learning the tools and platforms, as they do trying to rebuild them, we would be in a much better place
Related Rants
Swift 😐
Oh Swift why
This is how I write my header signatures ;)
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.
undefined
wk40
ios love
objective-c
swift