将 iPhone 应用程序移植到 Android？如何说服他们不这样做
我是一名签约 Android 开发人员，我讨厌人们要求我在 Android 上重新创建与 iPhone 应用程序相同的“外观和感觉”。
我如何才能让他们相信，使用标准 Android 导航和视图将使他们的应用程序比重新创建 Java 版本的 iPhone 应用程序更具吸引力。
链接赞赏。
I am a contracted Android developer, and I hate when people ask me to recreate the same "look and feel" that an iPhone application has on Android.
How can I convince them that using the standard Android navigation and views will make their application more attractive than recreating a Javaized version of an iPhone app.
Links appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
Android 用户有不同的期望，并且习惯于 Android 上占主导地位的操作。如果所有其他应用程序的行为与您的应用程序不同，则会恶化用户体验
Android users have different expectations and are used to the handling which is predominant on Android. It worsens the user experience if all other apps act differently from yours
我认为问你这个问题的人认为不同平台具有相同的外观和感觉将会统一体验。
对此，我认为最好的答案是，大多数 Android 用户不使用 iPhone，因此不习惯这种外观和感觉，也不关心该应用程序在 iOS 上看起来是否相同，因为他们从不使用它。然后你会发现一些应用程序很好地展示了 Android 框架的可能性，并且可能还利用了 iOS 上不可用的功能。当你有一堆应用程序（谷歌自己的应用程序通常已经相当不错，例如地图），它们具有相似的外观和感觉以及相似的用户体验范式时，他们可能会明白你的意思。
I think people that will ask you this question think that having the same look and feel for different platforms will unify the experience.
To that I think the best answer would be that most android users do not use an iPhone and are therefor not used to this look and feel and also don't care if the app looks the same on iOS, as they never use it. And then you could find some apps that showcase the possibilities of the android framework very well and maybe also take advantages of features not available on iOS. And when you have a bunch of apps (Googles own apps are usually quite good already, e.g. maps) that have a similar look and feel with similar UX paradigms they might get your point.
我过去使用过的一个论点是指出 Android 有一个内置的“后退”按钮。这可以采用物理按钮的形式（如大多数手机的情况），也可以采用内置在 UI 中的形式（如 Honeycomb 的情况）。在 iOS 上，“后退”行为通常由导航控制器处理，通常以 UI 按钮的形式出现在屏幕的左上角。
Android用户熟悉Android“返回”机制，iOS用户熟悉iOS“返回”机制。两者都同样好，但它们有本质上的不同，如果您使用与操作系统本身和其他应用程序的工作方式不一致的“后退”机制，它将使您的应用程序不太直观。
虽然这只是一个例子，但还有许多其他例子可以用来强化这一点。
One argument that I have used in the past is to point out that Android has a built-in "back" button. This can either take the form of a physical button, as is the case with most handsets, or one built in to the UI as is the case in Honeycomb. On iOS, "back" behaviour is usually handled by a Navigation Controller, often in the form of a UI button which appears in the top left of the screen.
Android users are familiar with the Android "back" mechanism, and iOS users are familiar with the iOS "back" mechanism. Both are equally good, but they are fundamentally different, and it will make your app less intuitive if you use a "back" mechanism which is not consistent with how the OS itself, and other apps work.
While this is but a single example, there are many other examples which can be used to reinforce this.
您可以尝试向他们解释这些是具有不同行为的不同平台。
也许列出不同行为的 UI 内容，并尝试通过具体示例向他们展示为什么 Android 用户在外观和感觉不同时会感到困惑（并因此停止使用他们的应用程序）。
You could just try to explain to them that these are different platforms with different behaviours.
Maybe make a list of differently behaving UI stuff, and try to show them on concrete examples why Android-users could get confused when things look and feel differently (and therefore stop using their app).