使用 Samsung Galaxy Tab 附加组件将如何影响/限制我的 Android Market 部署？
我已经针对此处提到的附加组件提供的新构建目标运行了我的Android应用程序。这似乎在模拟器中正常工作，但现在我非常不确定在向市场交付应用程序时使用此构建目标的影响。
看来我必须使用此构建目标才能使模拟器正常工作。一般设备都是这样吗？ （即）我可以针对标准 android/google API 进行构建并使其在实际的 Galaxy Tab 上正确运行吗？
如果我将具有此构建目标的应用程序部署到 Android 市场，这会对我已经运行的其他（较小屏幕）设备产生不利影响吗？ （即 Galaxy 选项卡“特殊酱汁”是 Android 功能的超集吗？我看到有人抱怨 Google 地图 API 无法在其中运行，等等。）
我的应用程序必须在市场上有两个版本吗？一种用于“标准”设备，另一种用于“大”屏幕设备？一款专门针对 Galaxy Tab？
当 Android Tablet vNext（无论是什么）出现并拥有自己的自定义插件和构建目标时，我是否必须克隆我的存储库并发布/维护该版本的设备特定版本（假设任何插件 - Galaxy 选项卡的特殊酱汁不会出现在 vNext 的附加组件中，也不会“兼容”）
我正在驾驶什么是我找不到可靠的文档来说明这样的附加组件将如何影响我的应用程序部署和维护的碎片。我希望能够支持新的 Android 设备，例如 Galaxy Tab，但我不想构建一堆一次性的特定于设备的应用程序实现。能够让一个应用程序在所有设备上运行不是重点吗？
预先感谢您对这种情况可能有的任何见解。
I have run my android app against the new build target provided by the add-on mentioned here. This appears to be working correctly in the emulator, but now I am very unsure as to the implications of using this build target when delivering an app to the marketplace.
It would appear that I have to use this build target to get the emulator to work. Is this true of the device in general? (i.e.) could I build against the standard android/google APIs and have it run correctly on the actual Galaxy Tab?
If I deploy an app with this build target to the Android market, will this adversely affect other (smaller screen) devices that I already run on? (I.e. is the galaxy tab "special sauce" a superset of Android functionality? I see grumbles about the Google APIs for maps not working in it, etc.)
Will i have to have two versions of my app in the market? One for "standard" devices and one for "large" screen devices? One for the Galaxy Tab specifically?
When Android Tablet vNext (whatever that may be) comes out and has its own custom add-on and build target, will I have to clone my repository and publish/maintain a device specific version of that (presuming that any add-on special sauce for the galaxy tab will not be in vNext's add on and will not be "compatible")
What I am driving at is that I can't find reliable documentation on how an add-on like this will affect the fragmentation of my app deployment and maintenance. I want to be able to support new Android devices like the Galaxy Tab, but I don't want to be building a bunch of one-off device-specific app implementations. Isn't the point to be able to have one app work on the gamut of devices?
Thanks in advance for any insight you might have on the situation.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您不需要使用三星提供的构建目标在 Galaxy Tab 上部署您的应用程序（绝对不是真正的设备，对我来说模拟器工作正常）。
我使用目标 SDK 4 (Android 1.6) 构建所有项目，它们在 Tab AVD 上运行良好。
三星建议中需要考虑的一个含义是，他们希望将 min SDK（与目标 SDK 不同）设置为 4，这将排除 Android 1.5 设备。您可能并不真正需要这样做，但应该进行测试以确定。
一般来说，硬件供应商（摩托罗拉、三星）：
- 一定要利用 AVD，特别是如果您没有购买真实设备的预算或者尚未提供该设备
- 不要使用自定义开发环境，坚持使用 Google 标准工具。
我的两分钱。
It's not the case that you need to use the Samsung-provided build target to deploy your app on the Galaxy Tab (definitely not the real device, and for me the emulator works fine).
I build all my projects with a target SDK of 4 (Android 1.6) and they run fine on the Tab AVD.
One implication of the advice from Samsung that needs consideration is that they want min SDK (not the same as target SDK) set to 4, which will exclude Android 1.5 devices. You probably do not really need to do this but should test to be certain.
In general with hardware vendors (Motorola, Samsung):
- do take advantage of the AVDs, especially if you don't have the budget for the real device or it's not yet available
- do not use the custom dev environment, stick with the Google standard tools.
My two cents.
这不应该是必需的。毕竟，大多数市场应用程序在 Galaxy 选项卡上运行得很好。唯一的问题似乎是 GT 模拟器没有安装 Google API，尽管实际设备安装了 Google API。但我可能想一回到办公室就检查一下。
好吧，我不这么认为，但无论如何你应该使用常规构建目标之一。 GT 插件仅通过指定 API 版本和设备参数来帮助您，不涉及任何特殊内容。
不，你不应该需要这样做。实际上，您无需更改应用程序中的任何内容即可使其在 GT 上正常运行，因为 Android 处理了大部分繁重的工作。不过，Android 不会帮助您为平板电脑提供不同的布局，因为它们尚未得到正式支持。但通过查看屏幕尺寸和密度，您仍然可以选择手动执行此操作。
简单地说，不。将来，平板电脑很可能会直接受到 Android 的支持，并且，如果当前的情况有任何迹象的话，它将提供多种方法来帮助您将应用程序应用于各种平板电脑设备，而无需分叉你的代码。
This shouldn't be required. After all, most market apps run just fine on the galaxy tab. The only problem seems to be that the GT emulator doesn't have the Google APIs installed, though AFAIR the actual device does. But I might want to check on that as soon as I get back to office.
Well, I don't think so, but you should probably use one of the regular build targets anyway. The GT plugin only helps you by specifying the API version and the devices parameters, there is no special sauce involved.
No, you shouldn't need to. You actually don't have to change anything in your app to make it run decently on the GT, since Android handles most of the heavy lifting. Android won't help you provide a different layout for tablets though, since they are not officially supported yet. But by looking at screen size and density, you can still choose to do so manually.
Simply put, no. In the future, tablets will most likely be supported directly by Android, and, if the current state of affairs is any indication, it will provide numerous ways to help you adopt your application for all kinds of tablet devices as well, without having to fork your code.