如何使用三星Galaxy Tab的附加影响/束缚我的Andr​​oid市场的应用？ [英] How will using the Samsung Galaxy Tab Add-on affect/fetter my Android Market deployments?

问题描述

我遇到我反对的附加提到提供了新的构建目标Android应用>。这似乎是在模拟器中正常工作，但现在我的使用提供一个应用程序推向市场时，这个构建目标的影响非常不确定。

1. 这样看来，我必须使用此构建目标，以获得模拟器的工作。这是一般的设备真的吗？ （即）我可以建立对标准的Andr​​oid / Google API和有它实际的Galaxy Tab上正确运行？




2. 如果我部署与此构建目标到Android Market的应用程序，这会造成不利，我已经运行在其他（小屏幕）设备影响？ （即是Galaxy Tab的特殊酱油的Andr​​oid的功能的超？我看到了谷歌的API在它不工作，等地图牢骚。）




3. 我将必须有我的应用程序的两个版本在市场上？一为标准的设备，一个是大屏幕的设备？一个用于Galaxy Tab的具体？




4. 在Android平板vNext（无论那是）出来，有其自己的自定义插件和建设目标，我会克隆我的仓库和发布/维持一个设备特定版本（presuming任何附加的Galaxy Tab的特制的酱汁不会是vNext的上添加并不会兼容）

我所驾驶的是，我无法找到如何一个附加这样会影响我的应用程序部署和维护的碎片可靠的文档。我希望能够支持像Galaxy Tab的新的Andr​​oid设备，但我不希望被建立一堆一次性设备特定的应用程序实现。是不是点能够对设备的色域一个应用程序的工作？

预先感谢您可能对局势的见解。

解决方案

  

这样看来，我必须使用
      这个构建目标，以获得
      模拟器工作。这是真
      在一般的设备？ （即）可
      我对建设标准
      安卓/谷歌的API，并让它运行
      正确的实际Galaxy Tab的？

这应该不是必需的。毕竟，大多数的市场应用运行的Galaxy Tab上就好了。唯一的问题似乎是，GT模拟器没有安装谷歌的API，虽然AFAIR实际设备支持。不过，我可能想只要我回到办公室检查了。

  

如果我部署此版本的应用程序
      目标到Android市场，将
      这造成不利影响其他（较小
      我已经运行的屏幕）设备
      上？ （即是Galaxy Tab的特
      酱油的Andr​​oid的一个超集
      功能？我看到牢骚
      谷歌的API进行地图不工作
      在它等）

好吧，我不这么认为，但你也许应该使用常规的构建目标之一呢。 GT的插件仅通过指定的API版本和设备参数可以帮助你，没有涉及特别的酱汁。

  

我将有两个版本
      我在市场上的应用程序？一个用于
      标准的设备，一种针对
      大屏幕的设备？一个用于
      Galaxy Tab的具体？

没有，你不应该需要。你居然没有任何改变在你的应用程序，使其对GT体面运行，由于Android处理大部分繁重的工作。 Android将不会帮你提供平板电脑不同的布局，虽然，因为他们没有正式被支持。但是，看着屏幕大小和密度，您仍然可以选择手动操作。

  

在Android平板vNext（无论
      这可能是）出来并且具有其
      自定义插件和建设目标，
      我会克隆我的仓库
      和发布/维护设备
      即（presuming的特定版本
      任何附加特殊酱
      Galaxy Tab的不会在
      vNext的加上并不会
      兼容）

简单地说，没有。在未来，平板电脑将很有可能直接搭载Android的支持，而且，如果事务的当前状态是任何迹象显示，它会提供多种方式，以帮助您采取的各种平板设备，以及应用程序，而无需叉您code。

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.

1. 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?

2. 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.)

3. 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?

4. 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.

解决方案

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.

这篇关于如何使用三星Galaxy Tab的附加影响/束缚我的Andr​​oid市场的应用？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！