77

!rant

I had to stop developing hybrid android applications with Ionic and start developing native.. I was given 1 week to present an app or they would hire an external developer.. I knew nothing about Java or Android development and in 4 days I already have a working, hardware scanner integrated, API calling, camera picture taking,.. Application! My brain hurts and I'm feeling like a zombie, but hey.. I'm proud of myself! :D

Comments
  • 4
    You rock! :D
  • 5
    You sir made this community proud. You're amazing!!!!
  • 1
    Way to go! Nothin can stop you know!
  • 4
    Great job man! Make sure to reward yourself with something nice when this is all over, you deserve it!!
  • 1
    You are the pinnacle of what motivation and passion produces! Good on you!
  • 0
    If you don't mind me asking, what did you use for learning?
  • 3
    but then what happens when you need to develop for iOS as well ?

    handling two code bases not gonna be a fun thing right ?
  • 3
    I'm proud of what you did... but IDK. I feel like that was a horrible position to put you in
  • 1
    @DarKneT Always a trade-off you make between app experience and development and maintenance effort.

    There are ways to help. Business and domain logic is agreed upon beforehand and is standardised across both platforms, as in, the class definitions, package structuring, APIs and so on.

    The platform specific stuff(UI, Sensors, Hardware) is developed independently and uses the standardised modules agreed upon.

    But yes, the code still has to be written and maintained twice.
  • 2
    That's why React Native appears to be really interesting. You can write the business logic once, and the UI dependant stuff for each device. Leveraging the maintainability of one code base, while still having native UI.

    The harder part'd be, as I could imagine, implementing business logic using utilities only available on one platform and not on the other.
  • 3
    @Rocket3G True, however React Native is not without its own set of issues, for example, scrolling performance on low-mid range phones. The reason being that they don't employ view recycling which we use extensively in native development, so in the end, it always comes down to the trade offs you're willing to make.
  • 0
    A marathon session, well done! But why was the hybrid route abandoned?
  • 0
    Haven't done hybrid apps yet but I feel that the android sdk is the best when it comes to developing an app quickly.
  • 0
    @gtek It had all the functionalities, but it lacked the smooth experience. Icons sometimes dissapeared when clicked on, slow loading, not that good looking font (on newer devices), swiping not that accurate,... You noticed that it wasn't native.

    I do recommend it for simple applications, but once you go larger, you notice the "lower quality" (:
  • 0
    @abennett0322 Mostly YouTube, an Android Studio Essentials book and StackOverflow, but mostly just trial and error :D
Add Comment