TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Why do such things like smartphone apps even exist if we have web pages?

16 点作者 foothebar超过 3 年前
Regarding how advanced today web technologies are, and how much stuff we can do in our web browsers – why do such things as (most) smartphone apps even exist? Even more: Most of these apps seem to fall into the category of providing a GUI for the functionality a server in the internet provides for it, so being a meaningless piece of software, where the creators have to program a different version for every platform, and are furthermore not allowed to do what they want, and have to share any payments with the platform providers, which get quite a piece of the cake.<p>Instead when directly using a web page, which can be used by every device, including desktop computers, they also would have access to the devices sensors, camera, microphone, audio, position, but would only have to program once, and would be free to do what they want, including payments going only to themselves.<p>So why do people provide (and use) apps, instead of proper web technology? Except of some really special ones (like banking), this does not seem to make any sense?

10 条评论

ksec超过 3 年前
I thought this is well known. Especially in 2022. If we could sum it up in two words it would be User Experience.<p>Games - Even though there are some games that could be done with HTML &#x2F; JS and there <i>are</i> games as such within app store. Vast majority require Native access for performance and battery.<p>Icons on HomeScreen. This is partially a platform limitation where you cant add the &quot;Web Site&quot; to Home Screen with &quot;one click&quot;. A click on Homescreen to access information is million times easier to typing in a Website address.<p>Performance - The best HTML &#x2F; JS apps may be just above the median of Native Apps in terms of performance. And vast majority of HTML &#x2F; Web Apps performs poorly even on the fastest SoC A15.<p>Technology - You cant do instant messaging and other things as native app.<p>App Store provide easy access, distribution and trust to consumers.<p>Basically the experience of Native Apps is so much better than Web alternative. That doesn&#x27;t mean I support native app or denounce Web App. I consider the point above as objective truth.
评论 #29738293 未加载
评论 #29738156 未加载
评论 #29746217 未加载
kasperset超过 3 年前
Steve Jobs had the similar idea so he opposed the idea of App store initially but as we know he gave up and we know the result. I think idea is to present &quot;containerized&quot; experience so the user thinks they are dealing with the app exclusively. There is some personal appeal to app whereas web page seems like a general purpose app which some users feel they may have subpar experience.<p>I think non-techie people are more accustomed to &quot;exclusiveness&quot; where you just reach the app directly as compare to having the choice the entering the webpage address or even clicking a bookmark. Sometimes it is more about human psychology than technical issues.
评论 #29736830 未加载
LinuxBender超过 3 年前
One factor may be that an app gives the developer full control of the client experience. If your web server application has to support a myriad of browsers, browser versions, browser addons, browser addon versions it could be quite challenging to make your site functional. Really clever developers might take that on as a personal challenge and puzzle to solve but corporations will not entertain such things.<p>I think the best one could do would be to contribute to a Hall Of Fame of websites that work well with cell phone browsers and create an icon legend that lists what addons are known to interfere with that site.<p>Beyond that maybe contributions to the next HTML<i>6&#x2F;7</i> specifications that which makes writing code that is more compatible with cell phone browsers and addons, giving more control to the client while keeping the site functional even when using addons. i.e. extensions in the spec that addons can utilize to better understand context and intention.
评论 #29737063 未加载
josephcsible超过 3 年前
The original reason is that they existed before Web pages were powerful enough to do all of those things. Today, it&#x27;s purely for evil reasons, e.g., to be able to refuse to run if root is detected, to be out of reach of adblocking browsers, or to be able to harvest more of your private data. Now on iOS, there&#x27;s still some ways that Web apps are lacking, but that&#x27;s an evil reason too: Apple bans all non-Safari engines, and intentionally limits Safari, so that they have control over everyone via App Store rules.
zaphar超过 3 年前
My phone doesn&#x27;t always have an internet connection, or the internet connection can be flakey. Many of the apps I have on my phone work without that connection I find it valuable. It also has the side effect of not introducing random performance problems caused by IO which translates to a smoother more pleasant user experience and better battery life. Web pages <i>really</i> want a network connection for the most part. It creeps in at weird places in the design and that constraint leaks all over the place.
h2odragon超过 3 年前
Add in the &quot;app only&quot; business that exist now, as an extra layer of frothy foolish frosting on the cake of stupid.<p>The &quot;touch screen tablet&quot; is the epitome of SciFi user interface and has been since the early 70s or so, I think. The &quot;powers that be&quot; have this in their sights and can&#x27;t hear any of the reasonable objections raised by engineers and users. One might conclude that the real reasons have less to do with &quot;user experience&quot; and more to do with what the vendors can get away with.<p>The humble keyboard, despite all the reasons there are to hate it, despite all the flaws and room for improvement; despite the lack of &quot;market support&quot; by manufacturing giants, still continues to be used, valued, and innovated on by users.<p>So the answer to your question is, I think: because BIG money <i>wants</i> there to be smartphones and apps; in the hope that that minimal functionality will prevent the invention of better functions. Competing is hard, so much easier to manage market expectations.
thatsamonad超过 3 年前
I don&#x27;t think I&#x27;ve seen this mentioned here so far, but a big reason why I use (and pay for) native apps is because the subscription management process, at least in the Apple ecosystem, is quite a bit simpler and less user hostile than having to go through an individual site&#x2F;company for each service.<p>If I subscribe through the App Store, I can easily cancel my subscription at any time by going to one place and just clicking &quot;Cancel Subscription&quot;. Contrast this with some well-known news sites who make you place a phone call and then give you the run around just to cancel a basic subscription.<p>It would be a nightmare to subscribe to multiple different websites and then have to go through a user-unfriendly process to cancel through each one.
评论 #29746233 未加载
GoldenMonkey超过 3 年前
Because the mobile web browser experience just sucks. Thin client vs rich client experience. It’s a downgrade to the basic common denominator experience.<p>And what amazing games are you playing on a web browser? The same could be said about desktop apps… Why even have desktop apps?
评论 #29737105 未加载
syspec超过 3 年前
The OP&#x27;s question is not sincere, they debate any point which is brought up.
评论 #29746268 未加载
DanielHB超过 3 年前
Well the answer is complicated but the main things are: 1. When smart phones first started (2007) web tech was not nearly good enough to make the experiences that the smart phones were capable of providing. So many things are still very hard or impossible to do in browser APIs (GPS, blu tooth, compass, gyro, push-notifications, etc). On top of that the Microsoft lawsuits over internet explorer in the early 2000s and the ActiveX&#x2F;Java Applets security issues made everyone very wary of adding or using custom platform-specific extensions to web apps. Sure Steve could have said: &quot;Hey build web apps, but if you want GPS, use this function that only works in iOS Safari&quot;, the would have been crucified by devs and lawsuited to hell by the US (on behalf of google and microsoft lobbyists). In fact look up Push API notifications in Safari, it is EXACTLY this and it is a huge pain for devs and the other companies on W3 are really annoyed at apple over it: <a href="https:&#x2F;&#x2F;developer.mozilla.org&#x2F;en-US&#x2F;docs&#x2F;Web&#x2F;API&#x2F;Push_API" rel="nofollow">https:&#x2F;&#x2F;developer.mozilla.org&#x2F;en-US&#x2F;docs&#x2F;Web&#x2F;API&#x2F;Push_API</a><p>2. Performance was a much bigger problem, especially for games and 3d acceleration APIs like webgl was also not available back then. To this day the 3d engines makers still don&#x27;t target the Browser platform because webgl is so limited and buggy. I think Unity did for a bit but eventually dropped support<p>3. In fact Steve Jobs around 2007 was pushing for web apps as the only 3rd party app platform for the iphone, but due to public pressure (due to 1. and 2.) App Stores came about. They still exist though because the vendors (google and apple) realised the lock-in and closed-garden control over the market was a huge boon for profits. Much like Playstation&#x2F;XBox&#x2F;Switch, they really enjoy taking a cut on every sale. Steve knew that when you are the underdog entering a market you have to be open and consumer friendly, once you have the users locked-in you can close down. He managed to hit the jackpot because there was NO viable <i>open</i> alternative to code what the phones were physically capable of, so the developers didn&#x27;t even have a choice, they HAD to use the proprietary solution. This is partly why the VR space is so promising to big companies, they know whoever gets lock-in effect will be able to milk it for DECADES. We as consumers and 3rd party devs desperately need an open VR platform (maybe inside the browser?), but it seems like it is not going to happen any time soon<p>The lock-in is much more insidious than you might think though, the lock-in is both in the user-level but as well as the developer-level. In UI development there is this big thing that the UI should feel native to the platform, meaning apps should behave similarly to each other. For example the acceleration and rubber-banding when scrolling down a list should be the same for every app.<p>Browsers are inherently a different platform that just happens to run on top of other platforms. Anyone can tell that a web app in Windows feels different than a Windows 8 App that also feels different to the obscure win32 configuration screens from windows 98 days that appear if you dig deep into the settings<p>Android and iOS likewise have the same lock-in effect, web-views wrapped in native apps just feel bad. Not because they are bad, but because they are different. The ONLY way to make a web app feel native in Android or iOS would be to compile their native UI Widgets into webassembly and somehow render them to a full-screen &lt;canvas&gt; tag and not use the DOM at all. Which is kinda pointless, might as well code full native. No matter how much hacking a cross-platform framework does to try to feel native it won&#x27;t be native because there is no way to mimic millions of lines of code of the native UI toolkit. It is much the same reason Java desktop apps and java applets failed, they didn&#x27;t feel native inside Windows OR inside browsers<p>Facebook realised this earlier and made React Native which renders to native UI Toolkit elements instead of using a web-view or drawing to screen directly. Google seems to be moving in this direction as well with Flutter, their core business are the apps themselves not the google play store and too many companies are going iOS-only for their apps so google is pushing an &quot;open&quot; platform (that they control)<p>On the other side you also have developers lock-in because all those platforms need separate dedicated developers, those devs will push back HARD on using any non-native tech because it literally means they their expertise is wasted and they will be downgraded from Senior iOS developer to Junior Web Dev. Just look at any company where business decides to shift to use web-wrapper native app, all the iOS&#x2F;Android devs quit immediately (even though the company would like to keep a few because of platform-specific quirks)<p>In short the answer is: &quot;Because it is good business for the companies that make the smartphones&quot;
评论 #29737705 未加载