Looking for a Hybrid App Developer

[[)roi(]]

I thought we went through this last night Driod?


Property24
https://play.google.com/store/apps/details?id=com.korbitec.property24

sword kit
https://play.google.com/store/apps/details?id=sworkitapp.sworkit.com

Fan React
https://play.google.com/store/apps/details?id=com.fanreact.app

Rio 2016
https://play.google.com/store/apps/details?id=com.ajay.internetcheckapp

Giro d'Italia
https://play.google.com/store/apps/details?id=com.gazetta.it.giro&hl=en

If it is good enough for http://www.giroditalia.it/eng/ then it is more than good enough for us.

Which leads me to believe News24's election app might also be one... (Would like if someone can confirm whether or not it is)

Nope, you again miss it. Indistinguishable? Maybe I'm wrong to assume our standards are the same?

 

[[)roi(]]

Web Apps can not be comparable to a native app, your list above is useless.

There's a reason why Facebook went native.

Exactly...

 

[stricken]

The limit in question is one thread per webview (technically 2 - CPU and GPU). The solution is to split views and subviews into seperate webviews. We have reached native performance this way, but in the end, the complexity and dev work involved could have well been allocated to native.

Point is, hybrid is not a show stopper if done right, it just reaches a point where dev time will equal or exceed native. It depends on your use cases and business requirements.

All technologies and stacks offer pro's and cons. I wouldn't slate hybrid just because native is faster on the UI due to multiple threads.

 

[mercurial]

Property24
https://play.google.com/store/apps/details?id=com.korbitec.property24

AFAIK, Property24 is made with Xamarin.

 

[Thor]

AFAIK, Property24 is made with Xamarin.

I stand corrected then, I was told it's a Hybrid App, but yea apart from that I can't back that statement up.

 

[xumwun]

The limit in question is one thread per webview (technically 2 - CPU and GPU). The solution is to split views and subviews into seperate webviews. We have reached native performance this way, but in the end, the complexity and dev work involved could have well been allocated to native.

Point is, hybrid is not a show stopper if done right, it just reaches a point where dev time will equal or exceed native. It depends on your use cases and business requirements.

All technologies and stacks offer pro's and cons. I wouldn't slate hybrid just because native is faster on the UI due to multiple threads.

Could you not get multiple threads with web workers?

 

[xumwun]

I stand corrected then, I was told it's a Hybrid App, but yea apart from that I can't back that statement up.

Looking inside the APK file, it's definitely not hybrid.

 

[[)roi(]]

I stand corrected then, I was told it's a Hybrid App, but yea apart from that I can't back that statement up.

Let me throw another curve ball; Nothing prevents native apps from integrating primarily with UIWebview; meaning; it's still quite possible that a lot of the property24 app is driven as a web app.

 

[[)roi(]]

Looking inside the APK file, it's definitely not hybrid.

Still not a guarantee that they didn't architect most of their UI around UIWebview. Meaning under the covers it could employ techniques that are similar in behaviour to Cordova.

 

[stricken]

Could you not get multiple threads with web workers?

Yes. Except the main point of hybrid I suppose is to be cross-platform, and iOS's webviews do not support web workers currently.