If it's going to be a desktop application, then build a desktop application. You could use a portable language (e.g. Java) to build it so you wont need to port it to several platforms.
I'm not sure I see very many advantages to building a browser based application if you're not going to host it on a server (why is this not an option?)
如果我给你一个选择，那就构建一个服务器应用程序。构建可以通过 REST 调用控制的应用程序。如果该应用程序有效，您可以选择构建桌面 GUI、Web GUI 或两者。毕竟，UI 应该只是应用程序的一小部分，如果您需要从 Web 切换到桌面（反之亦然），您不会希望重写所有应用程序。
I seriously doubt if anything that is answered here would help you much. If you apparently cannot think of a comprehensive list of cons and pros yourself, you apparently don't know about opportunities and bottlenecks on each platform. There are many factors to this decision, and a choice cannot be made based on a general list anyone would post here, without knowing what you want to build.
If I were to give you a choice, build a server application. Build an application that can be controlled by REST calls. If that application works, you can choose to build a Desktop GUI, a web GUI or maybe both. The UI should be just a small part of your application after all, and you wouldn't want to have to rewrite all of the application if you needed to switch from Web to Desktop or vice versa.
It depends on the features of the app. It is a simple data listing app with a small storage requirement, html5 based apps can be developed using technologies like AIR, Phonegap etc. If your app is very interactive, graphical based, and required very high performance, then Native may be a better go.
Going with HTML technologies gives the added benefit of targeting multiple platforms with one code base.
Try to evaluate the complexity of your interface, if you've got tons of data to show and tons of iteractions for the end user, just forget about web stuffs and go native.
Moreover, you need to clarify which language you intend to use. You can always resort to a web based GUI, but you will need to install on client machine at least a web server (or an application server if you go J2EE).
Regards
PS: from my point of view WWW is "JUST" a way to deliver content, not applications, HTML wasn't designed for complex graphics, and modern apps, just need a cool appeal (as long as you're not writing some mobile stuff with relatively simple interface).
发布评论
评论（4）
如果它是一个桌面应用程序，那么就构建一个桌面应用程序。您可以使用可移植语言（例如 Java）来构建它，这样您就不需要将其移植到多个平台。
如果您不打算将其托管在服务器上，我不确定构建基于浏览器的应用程序是否有很多优势（为什么这不是一个选项？）
If it's going to be a desktop application, then build a desktop application. You could use a portable language (e.g. Java) to build it so you wont need to port it to several platforms.
I'm not sure I see very many advantages to building a browser based application if you're not going to host it on a server (why is this not an option?)
我严重怀疑这里的回答是否会对您有很大帮助。如果您显然自己无法想到缺点和优点的全面列表，那么您显然不了解每个平台上的机会和瓶颈。这个决定有很多因素，并且在不知道您想要构建什么的情况下，不能根据任何人在此处发布的一般列表来做出选择。
如果我给你一个选择，那就构建一个服务器应用程序。构建可以通过 REST 调用控制的应用程序。如果该应用程序有效，您可以选择构建桌面 GUI、Web GUI 或两者。毕竟，UI 应该只是应用程序的一小部分，如果您需要从 Web 切换到桌面（反之亦然），您不会希望重写所有应用程序。
I seriously doubt if anything that is answered here would help you much. If you apparently cannot think of a comprehensive list of cons and pros yourself, you apparently don't know about opportunities and bottlenecks on each platform. There are many factors to this decision, and a choice cannot be made based on a general list anyone would post here, without knowing what you want to build.
If I were to give you a choice, build a server application. Build an application that can be controlled by REST calls. If that application works, you can choose to build a Desktop GUI, a web GUI or maybe both. The UI should be just a small part of your application after all, and you wouldn't want to have to rewrite all of the application if you needed to switch from Web to Desktop or vice versa.
这取决于应用程序的功能。它是一个简单的数据列表应用程序，存储需求很小，可以使用 AIR、Phonegap 等技术来开发基于 html5 的应用程序。如果您的应用程序交互性很强、基于图形并且需要非常高的性能，那么 Native 可能是更好的选择。
使用 HTML 技术还具有使用一个代码库针对多个平台的额外好处。
我有一篇关于 HTML5 vs Native vs Hybrid 在我的博客上。希望它有用。
It depends on the features of the app. It is a simple data listing app with a small storage requirement, html5 based apps can be developed using technologies like AIR, Phonegap etc. If your app is very interactive, graphical based, and required very high performance, then Native may be a better go.
Going with HTML technologies gives the added benefit of targeting multiple platforms with one code base.
I have a write up on HTML5 vs Native vs Hybrid on my blog here. Hope it is useful.
尝试评估你的界面的复杂性，如果你有大量的数据要显示，并且要为最终用户进行大量的迭代，那么就忘记网络内容并转向原生吧。
此外，您需要澄清您打算使用哪种语言。您始终可以使用基于 Web 的 GUI，但您需要在客户端计算机上至少安装一个 Web 服务器（如果您使用 J2EE，则需要安装一个应用程序服务器）。
PS：从我的角度来看
，WWW“只是”一种提供内容的方式，而不是应用程序，HTML 不是为复杂的图形而设计的，而现代应用程序，只需要一个很酷的吸引力（只要你不写一些界面相对简单的移动设备）。
Try to evaluate the complexity of your interface, if you've got tons of data to show and tons of iteractions for the end user, just forget about web stuffs and go native.
Moreover, you need to clarify which language you intend to use. You can always resort to a web based GUI, but you will need to install on client machine at least a web server (or an application server if you go J2EE).
Regards
PS: from my point of view WWW is "JUST" a way to deliver content, not applications, HTML wasn't designed for complex graphics, and modern apps, just need a cool appeal (as long as you're not writing some mobile stuff with relatively simple interface).