4 ms·
> If the experience is the same in HTML5 as the App Store, > then Apple loses What exactly Apple loses? It was the free app anyway, who cares? I don't get wh
by rimantas 14y ago
> If the experience is the same in HTML5 as the App Store,
> then Apple loses
What exactly Apple loses? It was the free app anyway, who cares?
I don't get where this stupid notion of Apple being anti-web comes from. Their goal is to sell as much devices as possible, and provide the best user experience possible on them, that's it. They don't firewall your web apps, do they?
Neither "native" devs care about killing the web, but for some reason uninformed webdevs cannot stand native apps and declare wars, battles and winning. Why? Makes yourself a favour, learn any of the native SDK just enough to make a semi-trivial app and you will clearly see what native provides and what webtech solutions severely lack and will be lacking, because the technology was not created with apps in mind.
Why it is so important to kill native in favour of web? How about learning (not really learning, just stopping to ignore) which is best for that and use accordingly? You need a website? Great, there is your HTML and CSS. You need performant app? Great, there is your SDK. You want a mix of both? Cool, take a good close look and choose wisely. Maybe mix of both.
I don't see a call to replace native desktop apps with HTML and JavaScript, why are people so hell-bent about all or nothing on mobile?
- mbesto 14y agoWhoa! > Why? Makes yourself a favour, learn any of the native SDK just enough to make a semi-trivial app and you will clearly see what native provides and what webtech solutions severely lack and will be lacking, because the technology was not created with apps in mind. First off, I ran a iOS native app dev team for 1.5 years and am a huge proponent of native apps. Attacking me personally is something frowned upon here. > I don't get where this stupid notion of Apple being anti-web comes from. It's simple. The iPhone experience is only valid when good apps are made. Imagine you're Lotus123 back in the 90s and Microsoft is trying to compete with you. Microsoft creates a product that can read/write Lotus123 files, but has superior functionality. This is the same with HTML/CSS on mobile. It's called backwards compatibility. It can be the greatest and weakest barrier to entry for any company in today's technology.