开发工作:Web 与应用程序

发布于 2024-09-28 03:59:57 字数 235 浏览 2 评论 0原文

开发工作而言,具有相同功能集网络前端智能手机应用之间的关系是什么样的?不同智能手机平台(iOS、symbian 操作系统、Android 等)的应用程序之间的开发工作是否存在任何具体差异忽略训练时间?一个总体的估计就完全让我满意了。 ;)

提前致谢, 弗林施。

what does the relation between a Web frontend and a smartphone App with identical feature sets look like regarding the development effort? Are there any specific differences regarding the development effort between Apps of different smartphone platforms (iOS, symbian OS, Android, etc.) ignoring training time? A general estimation would completely satisfy me. ;)

Thanks in advance,
Flinsch.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

乖乖公主 2024-10-05 03:59:57

我犹豫是否称其为估计,甚至是有根据的猜测,但也许通过提出一些想法,我可能会帮助您思考。

忽略任何特定的平台细节,我发现 Web 与 Native 的根本区别在于,在 Web 情况下,您需要做一些额外的工作:

a)。您的演示文稿与后端分离,中间可能有 HTTP。因此,需要编写服务以及需要处理与通知和/或轮询相关的问题。
b).您可能会使用浏览器进行演示,因此您将使用某种 JavaScript 类型的库,但这些库仍然很难驱动。

因此,如果您的目标是单一设备,我的猜测是编写本机代码可能比基于 Web 的代码快 50% - 假设您确实针对相同的功能。

似乎发生的事情是我们妥协了 Web 应用程序,在一定程度上减少了功能,从而减少了开销。

还有另一个因素,Web 应用程序的 UI 部分原则上是可移植的,因此实际上 Web 应用程序开发可能是一项合理的投资,即使它确实需要付出更多的努力。

我怀疑可移植性很可能最终成为主要考虑因素。

I hesitate to call this an estimate, or even an informed guess, but perhaps by putting down some ideas I might help your thinking.

Ignoring any particular platform specifics I see the fundamental difference of Web v Native is that in the Web case you have some extra work to do:

a). You have presentation separated from the backend, with probably HTTP in between. So there are services to write and issues concerned with notifications and/or polling to deal with.
b). You're likely using a browser to do the presentation so you will be using some JavaScript kind of library, and these are still hard to drive.

So, if you are targeting a single device my guess is that writing native code is likely to be 50% quicker than web-based code - assuming that you really are targetting identical function.

What seems to happend is that we compromise Web Apps, reducing functionality somewhat and hence the overhead is reduced.

Also there's another factor, the UI portions of the Web App are in principle portable, hence in fact the Web App development may be a reasonable investment even if it does take more effort.

I suspect that portability may well end up being a dominant consideration.

初与友歌 2024-10-05 03:59:57

具体差异?有很多,但每个都有自己的权衡:

  • UI:Web 应用程序具有主要浏览器支持的 CSS(HTML、XHTML、HTML5)规范(尽管有他们的问题)。对于智能手机应用程序,每个 UI 都必须根据根据应用程序构建的语言进行设计和实现。您可以有效地创建像 Winamp(具有皮肤)这样的应用程序。对于 Web 应用程序来说,与为每种不同的智能手机操作系统型号编写 UI 相比,这是一个相对快速的工作。
  • 使用语言/可移植性:在 Web 应用程序中,应用程序位于服务器中,因此每个请求都会发送到服务器并从服务器返回响应。这使得 1) Web 应用程序可以用任何选择的语言编写,因为最终用户永远不会看到服务器也不需要配置它,2) 它允许开发人员用他/她熟悉的语言编写。智能手机应用程序,为了让开发人员在所有智能手机操作系统上运行他的应用程序,他/她必须学习操作系统的编程语言,并学会移植他们的代码以在那里工作(如果可以移植)。这在 Web 应用程序中从来不存在。
  • 硬件限制:对于智能应用程序,开发人员必须了解手机的功能和限制。 Facebook(例如)本质上可以增加内存,并随着需求的增长添加新的服务器和集群环境。你无法通过智能手机应用程序做到这一点。您必须限制您的实施,使其以您所需的智能手机可以容纳的功能运行。

还有更多(请随意添加),但所有这些都是软件开发人员如果想要进入所选领域就必须考虑的开发工作的一部分。

specific differences? There are plenty, but each with their own tradeoff:

  • UI: Web applications have CSS, (HTML, XHTML, HTML5) specifications that is supported by major browsers (although have have their issues). For Smartphone apps, each UI has to be designed and implemented according to the language the apps can be built on. You can effectively create apps like Winamp (having skins). For web applications, this is relatively a quick effort compared to writing UI's for each different smartphone OS models out there.
  • Language of use/Portability: In Web applications, an application sits in a server, so every request is sent to the server and response is returned from it. This allows that 1) Web applications can be written in any language of choice, as the end user never sees the server nor needs to configure it, 2) It allows the developer to write in a language that he/she is comfortable in. In smartphone apps, for the developer to run his apps to all the smartphone OS'es, he/she has to learn the programming language for the OS, and learn to port their code to work there (if porting is possible). That never exists in Web applications.
  • Hardware limitations: For smartapps, the developer must be aware of the cellphone capabilities and limitations. Facebook (e.g.) can essentially grow their memory, and add new servers and cluster their environment as the demand grows. You can't do that with smartphone apps. You will have to limit your implementation to run in a capability that your desired smartphone can accommodate.

There are more (feel free to add) but all these are part of the development effort that a software developer has to look at if they want to go a a field of choice.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文