4
hzlae
15d

I'm having such hard time adjusting with hybrid mobile development coming from native it frustrates meeeee :(

Comments
  • 3
    Don’t give into Satan and his false “write once deploy anywhere” promises. Return to us and return to native development
  • 0
    Which framework? :)
  • 1
    native FTW !
  • 0
    @practiseSafeHex I need you to talk to my employer asap. Dude u gotta be my lawyer!!! Lez fight for native!
  • 1
    @hzlae you want me to explain to someone that hybrid is shit?

    *cracks knuckles*

    ... I may have a few comments off the top of my head

    Which shitty tool you using anyway?
  • 0
    @practiseSafeHex Yes please! Well, they want me to learn Ionic because I had to finish a project
  • 0
    @badcopnodonuts Ionic, is it too late? :D
  • 1
    @hzlae well three results from google that help a little:

    "Your hybrid app is going to kill you": https://medium.com/teach-code/...

    "What do mobile devs think of ionic":
    https://quora.com/What-do-mobile-de...

    *note all the web devs saying its amazing because they don't have to learn mobile? Yeah that in itself is the problem. Web and mobile are not the same you can't just skip learning the platform you are now working on. Mobile devs don't use some shitty tool and say "thank god I don't have to learn about security for my backend"

    "What is your opinion":
    https://reddit.com/r/androiddev/...

    *"good for startups that can't afford development ... then they hire someone else to re-write it natively" - building something badly with the intention of throwing it away is just a waste of everyones time and money
  • 1
    @practiseSafeHex It’s still business decisions that drive things and those Frameworks are maturing everyday. If it means you can get to market and revenue faster and leaner I don’t feel that the trade offs are that bad. We as devs get too caught up in how things are supposed to be done “properly”... staying in business giving the best customer experience possible within means (they don’t know it’s not entirely native if load times are similar) and keeping people employed is priority number one.
    And as far as security goes no amount of best practice will stop a determined Individual who’s set his sights on your product.

    And framework or not, no self respecting dev would ignore fundamental security best practices.
  • 1
    @badcopnodonuts you've touched on some good points, but the reality of hybrid is far from the picture you've painted.

    I've used almost all of these tools before and they are horseshit. This isn't a case of a developer saying "my preference is to do it this way", this is a case of me incurring an issue that HTC one S, running Android 4.0.1 is unable to drop a pin on a map using titanium. Why? because its buggy as fuck. How do I fix it? I can't, its buried deep in the tool and completely unaccessible. I spent more time debugging that (because guess what phone and version the CEO had?) than building the app entirely.

    But thats one example right? Nope. I once spent 1h 45mins in titanium just to get it to launch the app in the Android simulator. It was so annoying and painful I ended up emailing the .apk to a friend and asked him to look at it. Took 48 hours to do a basic test.

    Cordova wouldn't let us integrate with a tool the entire company depended on.
  • 1
    @badcopnodonuts

    Xamarin introduced "Autolayout" which follows its own rules to Apples Autolayout and is impossible to search on google because they are named the same.

    The app i'm on now has a component in react-native from another team. There is a new bug in RN that causes Xcode to try and hold onto 20 new ports every 2 seconds, sending my brand new mac laptop with an i9 processor into a fucking meltdown every-time I try to run the app.

    Hybrid tools are only ok if the app is extremely basic. So basic I often ask the question is it needed and would a responsive website not be more appropriate. You spend more time dealing with random bullshit only related to the hybrid tool than building the feature, with no support because the community is 1% of the size. It is much quicker, easier and safer to do it native, and the end result of an app that works more reliably, with a smaller download, less of a battery drain and easier to maintain is what end customers want
  • 0
    @practiseSafeHex you make a valid point in regards to this. However depending on your business model and features, that small extra development overhead could be far outweighed by the savings of not having 3 teams maintain 3 or 4 different platforms over time. Once the foundations are in place, feature additions and updates should and mostly are straight forward.
    Even community stuff in the Cordova space is pretty solid.
    I looked into using react native for a project but react native web is still not really production ready so it would still require lots of diligence and planning.
Your Job Suck?
Get a Better Job
Add Comment