FarligOpptreden
Executive Member
- Joined
- Mar 5, 2007
- Messages
- 5,396
PM sent
I hear you, well I don't think the company is closed to the idea of native development, I think it just becomes a issue of the code base since with a native app there is only one code base.
I'm not here to debate native vs hybrid we all know the outcome I just think price and entry into market would be easier/faster/affordabler going the native route vs hybrid.
So I guess if your a native developer feel free to contact as well it can't hurt.
(I still believe native app development is a intermediate technology it has to exist now, but it will die out as Javascript HTML and css grows up) - that's just my personal opinion in my personal capacity, not related to this job offering at all.
Yeah, me neitherI hear you, well I don't think the company is closed to the idea of native development, I think it just becomes a issue of the code base since with a native app there is only one code base.
I'm not here to debate native vs hybrid we all know the outcome I just think price and entry into market would be easier/faster/affordabler going the native route vs hybrid.
Yeah that usually the idea for something considered outside of the norm; e.g. even Twitter outsourced it's desktop app build and ongoing maintenance. In your case what's the point (re contact); it's obviously going to be more expensive to build a native app for each OS vs. a generic web.I So I guess if your a native developer feel free to contact as well it can't hurt.
Not likely IMO; standardisation is the problem; there is no profit or notoriety in doing it exactly the same as everyone else, and that's assuming all the technical factors can be overcome.(I still believe native app development is a intermediate technology it has to exist now, but it will die out as Javascript HTML and css grows up) - that's just my personal opinion in my personal capacity, not related to this job offering at all.
It really depends on how far you want to stretch the fallacy; for that Android is probably the worst (not all versions are the same, neither are the devices), and it's exponentially worse for web apps.Good point on standardization.
Although I might be a bit confused/misunderstanding what you refer to with that.
As I was under the impression using native means the user would get to grips with the app quicker as the native UI is a standardized ui across all android platforms?
[)roi(];18125639 said:It really depends on how far you want to stretch the fallacy; for that Android is probably the worst (not all versions are the same, neither are the devices), and it's exponentially worse for web apps.
Bit more on web apps: long has it been argued that neither Apple, Google or <insert company here> don't expose their full API to web apps (its obvious why they don't) -- meaning the web app is likely to be using a generic API (nothing fancy, new or spectacular) and more often than not, will feel quite alien to the OS it runs on.
Simple test if I'm wrong; identify one web app that after it's launched is indistinguishable from a native app. i.e. I'll be surprised when you tell me.
It really doesn't change anything, if the code that ultimately runs on your device resides on a web server, then the same limits apply. The browser security model is always going to restrict what you can do, and the APIs you have access to are always going to be limited (as I reasoned before)Regarding that last part of your post
(NO argument on the rest I understand that.)
When I refer to hybrid apps I am talking about the Cordova apps just want to make sure that we are on the same page.
This is the property24 app downloaded from the play store
[)roi(];18125769 said:It really doesn't change anything, if the code that ultimately runs on your device resides on a web server, then the same limits apply. The browser security model is always going to restrict what you can do, and the APIs you have access to are always going to be limited (as I reasoned before)
Unless you have some other understanding of this; if so please share?
Sure, but remember if the code stills run in a webkit instance, then the same rules apply, otherwise it's just a native app. Just checked Cordova uses UIWebview or WKWebview; both instances of webkit; meaning it's the same result/same issues/same restrictions.I was under the impression using Cordova/phonegap wraps the application up and the code runs on the physical hardware and have access to all the phone features it's just the saving of data that happens on a shared SQL dB on a web server somewhere in the cloud.
Hybrid apps are basically web apps hidden behind a native app shell. Most of hybrid apps are built using cross-compatible web technologies (HTML5, CSS, Javascript etc.) and then they are wrapped in a native app using platforms such as Cordova.
[)roi(];18125833 said:Sure, but remember if the code stills run in a webkit instance, then the same rules apply, otherwise it's just a native app. Just checked Cordova uses UIWebview or WKWebview; both instances of webkit; meaning it's the same result/same issues/same restrictions.
Here's an explanation:
Confused; Ionic is a web app framework?Ahh I understand. Well then I think I can say this opportunity is open to both hybrid and native developers.
[)roi(];18125833 said:Sure, but remember if the code stills run in a webkit instance, then the same rules apply, otherwise it's just a native app. Just checked Cordova uses UIWebview or WKWebview; both instances of webkit; meaning it's the same result/same issues/same restrictions.
Here's an explanation:
[)roi(];18126757 said:Confused; Ionic is a web app framework?
A web app implies a single generic code base across iOS, Android, etc. Native apps implies a separate codebase & design for each; meaning I can't see how this would ever be comparable; re it's not the same amount of effort.
Sure with limited marshalling via public plugins. It still doesn't address the limitations / issues;Hybrid apps can use native API's. You can expose Java/Obj C to the java-script side.
Comparable, Really? So what's your reasoning behind why a majority of Apps are still built natively.both can be installed via google play store and the iOS store and runs as apps so it is definitely comparable.
[)roi(];18127169 said:Comparable, Really? So what's your reasoning behind why a majority of Apps are still built natively.
PS. I'd really would love to see a web app that you believe is either comparable to a native app, or better.
Native apps will always be better... There's no argument.
I hear you, well I don't think the company is closed to the idea of native development, I think it just becomes a issue of the code base since with a native app there is only one code base.
I'm not here to debate native vs hybrid we all know the outcome I just think price and entry into market would be easier/faster/affordabler going the native route vs hybrid.
So I guess if your a native developer feel free to contact as well it can't hurt.
(I still believe native app development is a intermediate technology it has to exist now, but it will die out as Javascript HTML and css grows up) - that's just my personal opinion in my personal capacity, not related to this job offering at all.
[)roi(];18125575 said:Yeah, me neither
Yeah that usually the idea for something considered outside of the norm; e.g. even Twitter outsourced it's desktop app build and ongoing maintenance. In your case what's the point (re contact); it's obviously going to be more expensive to build a native app for each OS vs. a generic web.
Not likely IMO; standardisation is the problem; there is no profit or notoriety in doing it exactly the same as everyone else, and that's assuming all the technical factors can be overcome.
Web Apps can not be comparable to a native app, your list above is useless.You need to read threads more thoroughly.
==========
Web Apps can not be comparable to a native app, your list above is useless.
There's a reason why Facebook went native.