是否有可能另外使用跨平台解决方案或集成他们的 api
最近几周我一直忙于跨平台开发的问题。首先是一个问题，我需要为 MoSync 的通信 API 编写一个包装器（我之前不知道这个 SDK 和其他 cpd）。例如，它应该在我们的 Java 环境中使用，以轻松创建与不同手机的蓝牙连接等。
对我来说，现在的另一个问题是，如何在现有项目中使用 MoSync、Titanium 等 SDK？我认为这是不可能的。要么开发 nativ，要么使用 cpd 框架。
我也想知道你什么时候推荐这个框架（我已经知道还有一些关于这个的其他线程）。我个人认为，由于技术缺陷和依赖性，这个 SDK 没有美好的未来。此外，跨平台解决方案（混合、解释、交叉编译器）的市场至少与移动操作系统本身的市场一样分散，
您的经验是什么？
马丁
In the recent weeks I have been busy with the issue of cross-platform development. That starts with the problem that I had the feeding to write a wrapper for the communication-API of MoSync (I don´t knew this SDK and others for cpd before). It should be used in our Java environment for instance to easy create a bluetooth-connection to different phones and so on.
For me the other question is now, how I can use such SDKs like MoSync, Titanium and others in a existing project? In my opinion it is not possible. Either you develop nativ or with a cpd-framework.
I would also be interested in when do you recommend this frameworks (I know already that there are some other threads about this). I personally would say that there isn´t a great future for this SDKs because of technical drawbacks and dependencies. In addition, the market for cross-platform solutions (hybrid, interpreted, cross-compiler) is at least as fragmented as the market for mobile operating systems themselves
What are your experiences?
Martin
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
任何类型的跨平台实施，无论是在移动设备上还是在任何地方，主要是为了缩短上市时间。这种说法可能看起来过于简单化，但或多或少是正确的。因此，使用它的理想情况是拥有一个应用程序/游戏，它可能使用智能手机功能的共同点，其中可能包括触摸、良好的用户界面、网络，在某些情况下可能还包括加速度计 LBS。因此，您可以更快地开发多部手机并降低开发成本。
如果您希望利用大量硬件特定功能，那么我们就进入了通常所说的未知领域。然后你必须做人们经常做的事情，收集更多关于目标手机领域的信息，看看“选择的框架”是否有能力在这些平台上提供功能。在这种情况下，您不可能部署现成的。
Cross-platform implementations of any type, on mobile or anywhere, are primarily to reduce the time to market. That statement may look like oversimplified, but it more or less holds true. So, the ideal situation to use it would be to have an application/game that maybe, uses the common denominator of features across the smartphones, which could include touch, a decent UI, the network, maybe the accelerometer in some cases LBS. So, you land on multiple phones in quicker time and reduced development cost.
If you are looking to utilize a lot of hardware specific features, then we land into what's commonly known as the unknown territories. Then you have to do what people always do, gather more information about the landscape of phones to target and see if the "chosen framework" has the power to dish out the features on those platforms. In this case, you cant possibly deploy one off-the-shelf.