Hacker Newsnew | past | comments | ask | show | jobs | submit | rstarback's commentslogin

The A.I. Command Search feature is absolutely nuts, I'm blown away


Scoop|Sr.iOS Engineer & Sr.Android Engineer|San Francisco, CA|Full Time|Onsite|www.takescoop.com/careers

Scoop brings co-workers and neighbors together to enjoy a smooth carpooling experience—unlocking new opportunities to create friendships, improve their well-being, and make the most of their valuable time.

Learn more in Crunchbase: https://news.crunchbase.com/news/scoop-raises-60m-for-corpor...

In this role, you will:

* Provide technical leadership and architectural guidance

* Represent engineering to collaborate with product managers on product features

* Partner with the CTO and technical leads to shape architectural vision and engineering roadmap

* Coach and mentor other engineers on design principles and best practices

* Work on engineering and company-wide initiatives

You should:

* Be knowledgeable about the iOS ecosystem and user interactions

* Care deeply about quality


I disagree with the author that "the Hybrid approach is the right choice for your next app".

Speaking from personal experience, the time it takes to create workarounds for UIWebView/WKWebView is only slightly less than the time to get familiar with Swift/UIKit. With knowledge of mobile paradigms it is easy to pick up Java/Android.

The advantages of creating two separate native apps are designs that fit each individual platform, better battery life, and overall better performance.

The author's time to market using hybrid development was less than the time it would've taken to learn iOS/Android native development and ship. However, the time difference is not as large as one may think. By continuing to invest in hybrid app development the author didn't learn valuable iOS/Android native app development skills and created an app that isn't as performant or designed to fit each platform.


  the time it takes to create workarounds for UIWebView/WKWebView is only 
  slightly less than the time to get familiar with Swift/UIKit
This times a thousand. I have wasted untold hours on clever paperclip-and-gum techniques to get WKWebView to be something it isn't: predictable and usable.

I still develop hybrid apps for clients (glorified web pages, really) but for personal projects I will never, ever go back. Kicking myself for not learning Swift earlier.


When my job looked at the JS app idea (3 or so years ago) that was one of my big takeaways. If we made a web app, we would spend just as much of not more time polishing it until it felt native than we would have making it native on the platform in the first place. It wasn't a highly complicated app.


"The author's time to market using hybrid development was less than the time it would've taken to learn iOS/Android native development and ship."

So in other words, he spent less than 50% of the time needed to build both an iOS and Android app (if we assume learning Java and building the Android app will take equally as long as learning Swift and building the iOS one). Sounds like a huge win if one can live with the other tradeoffs.


I use this frequently at work! :D


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: