Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "mobile hybrid dev"
Was free at work so applied for a stretch project.
PM: you know mobile dev?
Me: yes, built a few apps
PM: good, we have an old app we want you to take the JAR change everything but the look of it and make it a new hybrid app with the required features.
Me: *kill me please*
PM: and use WordPress as the server.
Accepted the challenge. Did the entire app in ionic and build a server for it with SpringBoot. Client loves it PM is still doesn't know😂2
Final interview for a native Android remote job via Skype
Client: Should we make a hybrid app instead?
Me inside: fucking hybrid app, hell no, the job posting was for a native mobile dev, and hybrid apps are shit
Me: We could have so much flexibility and can adjust so much better in the future when adding features when we go for a native mobile app
*phew* I almost lost my calm back there
Need some opinions. Joined a new company recently (yippee!!!). Just getting to grips with everything at the minute. I'm working on mobile and I will be setting up a new team to take over a project from a remote team. Looking at their iOS and Android code and they are using RxSwift and RxJava in them.
Don't know a whole lot about the Android space yet, but on iOS I did look into Reactive Cocoa at one point, and really didn't like it. Does anyone here use Rx, or have an opinion about them, good or bad? I can learn them myself, i'm not looking for help with that, i'm more interested in opinions on the tools themselves.
My initial view (with a lack of experience in the area):
- I'm not a huge fan of frameworks like this that attempt to change the entire flow or structure of a language / platform. I like using third party libraries, but to me, its excessive to include something like this rather than just learning the in's / out's of the platform. I think the reactive approach has its use cases and i'm not knocking the it all together. I just feel like this is a little bit of forcing a square peg into a round hole. Swift wasn't designed to work like that and a big layer will need to be added in, in order to change it. I would want to see tremendous gains in order to justify it, and frankly I don't see it compared to other approaches.
- I do like the MVVM approach included with it, but i've easily managed to do similar with a handful of protocols that didn't require a new architecture and approach.
- Not sure if this is an RxSwift thing, or just how its implemented here. But all ViewControllers need to be created by using a coordinator first. This really bugs me because it means changing everything again. When I first opened this app, login was being skipped, trying to add it back in by selecting the default storyboard gave me "unwrapping a nil optional" errors, which took a little while to figure out what was going on. This, to me, again is changing too much in the platform that even the basic launching of a screen now needs to be changed. It will be confusing while trying to build a new team who may or may not know the tech.
- I'm concerned about hiring new staff and having to make sure that they know this, can learn it or are even happy to do so.
- I'm concerned about having a decrease in the community size to debug issues. Had horrible experiences with this in the past with hybrid tech.
- I'm concerned with bugs being introduced or patterns being changed in the tool itself. Because it changes and touches everything, it will be a nightmare to rip it out or use something else and we'll be stuck with the issue. This seems to have happened with ReactiveCocoa where they made a change to their approach that seems to have caused a divide in the community, with people splitting off into other tech.
- In this app we have base Swift, with RxSwift and RxCocoa on top, with AlamoFire on top of that, with Moya on that and RxMoya on top again. This to me is too much when only looking at basic screens and networking. I would be concerned that moving to something more complex that we might end up with a tonne of dependencies.
- There seems to be issues with the server (nothing to do with RxSwift) but the errors seem to be getting caught by RxSwift and turned into very vague and difficult to debug console logs. "RxSwift.RxError error 4" is not great. Now again this could be a "way its being used" issue as oppose to an issue with RxSwift itself. But again were back to a big middle layer sitting between me and what I want to access. I've already had issues with login seeming to have 2 states, success or wrong password, meaning its not telling the user whats actually wrong. Now i'm not sure if this is bad dev or bad tools, but I get a sense RxSwift is contributing to it in some fashion, at least in this specific use of it.
I'll leave it there for now, any opinions or advice would be appreciated.16
fuck it, tell me straight.
Can i live into this tech world with poor math skills and no interest in web dev and designing?
my experience as native mobile dev was enjoyable and still is, but i fear that this is not a very broad career choice.
You see their is blockchain, dapps , hybrid apps, webapps, server designing, tensorflow models and Ai models( though they can be integrated with native apps too i guess ) , and many more tech and therefore jobs that rely on knowing about the webdev. and all i know is how to make a decent native java app.
and why the fuck should i join this web dev cult? its such a fucking mess. 8 different types of text sizes sizes, <b> and <strong> being the same thing, do you know about a thing called abstraction? My android studio would give me fucking murder warnings if i even dared to introduce hard coded texts along with code. and here, an html page is basically text + attributes? fucking kill me.3
You know there's something seriously wrong with a "framework" when it takes 20 minutes to figure out how to SHIFT A BUTTON INSIDE A HEADER.
Fuck you jQuery Mobile. I wish you had never been born.