我已经针对这里提到的附加组件提供的新构建目标运行我的Android应用程序。 这似乎在模拟器中正常工作，但现在我非常不确定在向市场交付应用程序时使用此构建目标的含义。
看来我必须使用这个构建目标来使模拟器工作。 一般来说这个设备是真的吗？ （即）我可以构建标准的android / google API并让它在实际的Galaxy Tab上正确运行吗？
如果我将具有此构建目标的应用程序部署到Android市场，这是否会对我已运行的其他（较小屏幕）设备产生负面影响？ （即，星系标签“特殊酱”是Android功能的超集吗？我看到关于谷歌API的地方不适用的地图等等）
我必须在市场上有两个版本的应用程序吗？ 一个用于“标准”设备，一个用于“大型”屏幕设备？ 一个专门针对Galaxy Tab的？
当Android平板电脑vNext（无论可能是什么）出来并拥有自己的自定义附加组件和构建目标时，我是否必须克隆我的存储库并发布/维护特定于设备的版本（假设任何附加特殊酱对于galaxy选项卡将不会在vNext的添加中，并且不会“兼容”）
我正在推动的是，我无法找到关于这样的附加组件如何影响我的应用程序部署和维护碎片的可靠文档。 我希望能够支持像Galaxy Tab这样的新Android设备，但我不想构建一堆一次性设备特定的应用程序实现。 是不是能够让一个应用程序在设备的全部范围内工作？
提前感谢您对此情况的任何见解。
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.
最满意答案
看来我必须使用这个构建目标来使模拟器工作。 一般来说这个设备是真的吗？ （即）我可以构建标准的android / google API并让它在实际的Galaxy Tab上正确运行吗？
这不应该是必需的。 毕竟，大多数市场应用程序在Galaxy选项卡上运行得很好。 唯一的问题似乎是GT模拟器没有安装Google API，尽管实际设备有AFAIR。 但是一旦我回到办公室，我可能想要检查一下。
如果我将具有此构建目标的应用程序部署到Android市场，这是否会对我已运行的其他（较小屏幕）设备产生负面影响？ （即，星系标签“特殊酱”是Android功能的超集吗？我看到关于谷歌API的地方不适用的地图等等）
好吧，我不这么认为，但你应该使用其中一个常规构建目标。 GT插件只能通过指定API版本和设备参数来帮助您，不需要特殊的酱料。
我必须在市场上有两个版本的应用程序吗？ 一个用于“标准”设备，一个用于“大型”屏幕设备？ 一个专门针对Galaxy Tab的？
不，你不应该。 实际上你不需要改变你的应用程序中的任何东西，以使它在GT上运行得体，因为Android处理了大部分繁重的工作。 Android不会帮助您为平板电脑提供不同的布局，因为它们尚未获得官方支持。 但是通过查看屏幕尺寸和密度，您仍然可以选择手动执行此操作。
当Android平板电脑vNext（无论可能是什么）出来并拥有自己的自定义附加组件和构建目标时，我是否必须克隆我的存储库并发布/维护特定于设备的版本（假设任何附加特殊酱对于galaxy选项卡将不会在vNext的添加中，并且不会“兼容”）
简单地说，不。 在未来，平板电脑最有可能直接由Android支持，如果目前的状况有任何迹象，它将提供多种方式来帮助您采用各种平板电脑设备的应用程序，而无需分叉你的代码。
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?
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.
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.)
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.
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?
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.
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")
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.
更多推荐
发布评论