This article addresses a few issues to such an extent that you can approach mobile engineers with a superior comprehension of what's required. You have to settle on who is going to port iOS to Android application and if this won't be the engineer, in a perfect world do this in conjunction with the designer.
The Android Market
Firstly, why produce for Android? These numbers for a year ago show overall Android share at more than 80%.
This has brought about financial specialists demanding Android versions of iOS applications and proprietors/originators finding that they are passing up a great opportunity for a huge cut of the market. In any case, it's an alternate market. Most applications are free as opposed to paid. Not very many Android paid applications are suitable. You have to consider rather freemium techniques and in-application buying which may influence the outline of your application.
The Android Market itself is interested in all. There's no audit system which implies your application can do things that won't have been conceivable under Apple's terms and conditions. Once more, this may influence how you outline your Android application. Application redesigns are practically momentary which implies less baffled end clients when there's an issue with your application. Applications can likewise be appropriated outside the Android Market as essentially as putting them on your site or disseminating by means of email. Be that as it may, in the event that you do this you may get a kick out of the chance to incorporate extra redesign identification and download into your application.
Plan for Android
I get excessively numerous occupation specifications that have wireframes that looks like the iPhone screens. The issue is that numerous plan instruments simply have iOS layouts as a matter of course and individuals think they can utilize them to outline Android applications. These plans strife with the look and feel of the gadget and really require a fundamentally additional push to actualize. For instance, making an Android catch or a rundown appear as though it does on iOS requires additional exertion. The primary issue regions are round catches as opposed to square, tabs at the base as opposed to the top, records with right directing bolts, off base symbols for normal capacities and back route by means of a top back catch.
The initial step is not to utilize iOS plan devices. When I am in charge of the outline I tend to simply utilize drawing instruments. I utilize Photoshop however you can utilize your most loved drawing instrument.
Consider Device Variety
As of Android 3.0, Google changed the way applications can be architected inside to take into account both Smartphone and Tablet formats. In the meantime, they presented a product Action Bar at the highest point of the screen as opposed to utilizing a product or equipment menu key at the base of the screen. As of Android 4.0, all new applications both Smartphone and Tablet began to utilize an Action bar. As of Android 5.0, new applications began to utilize Material outline.
Google give a similarity library that permits the most recent UI components to keep running on much more seasoned Android gadgets back similarly as Android 1.6. This permits one application to bolster all forms of Android while keeping up a predictable look and feel.
At the point when re-outlining your application you ought to consider how information and representation will be shown on much bigger and littler screens (than iOS). You additionally need to consider vertical and even perspective proportions.
Code Porting
It's impractical to take Objective-C and port iOS to Android. Android applications utilize for the most part Java despite the fact that c can likewise be utilized (called) from Java. In the event that your iOS application utilizes vanilla c (i.e. ordinary plain c code) then it's conceivable to re-utilize that code on Android. This is valuable for doing port iOS to Android complex libraries or giving expanded execution (e.g. picture handling). Be that as it may, Android has fundamentally fewer libraries accessible for the c code to utilize and regularly subordinate c libraries likewise need to port.
Sharing
A typical mix-up I see in UI plans is to insert sharing too profoundly into the application. Particulars some of the time incorporate UIs that accumulate data to be sent to Twitter,facebook or wherever. There is no requirement as for port iOS to Android. Rather, consider utilizing ACTION_SEND Intents which essentially hand off connections or content to other (introduced) applications, for example, Twitter and Facebook. The OS handles the interface. It's flexible to the point that whatever you do is present, for instance, some content and the OS will exhibit all the applications that can deal with the content. This implies clients will have the capacity to consequently share to different applications, for example, email or Evernote (in the event that they have it introduced). The reward for designers is that there's no compelling reason to compose code against the different server-side sharing APIs.
Expending
The absolute opposite of sharing is having the capacity to expend information sent by means of ACTION_SEND Intents. In the event that your application can deal with a typical organization, for instance,pictures, music or content then it may bode well to give an interface so that different applications can send you data.
Execution
Java is slower that incorporated Objective-C. You ought to consider what parts of your application are time touchy. This may prompt to changes in ability or outline, for instance, utilization of local c code, or option extraordinary systems to forestall Java rubbish gathering.
Information Sizes
Java has a generally little store estimate (working memory size to the layman) contrasted with iOS. This implies, for instance, it's impractical to open pictures full size. This may affect your application and you may need to do things any other way or move the code to c where there's no such confinement.
Additional Capabilities
You may have found a few things weren't conceivable on iOS that may now be conceivable on Android. For instance, Android can see all Bluetooth LE (iBeacon) gadgets in the region while iOS applications can just observe those it has pre-announced, by UUID, it wishes to see. Another illustration is that Android permits guide access to NFC. Additional elements in Android may make you reexamine your plan.
Security
Android Java applications are anything but difficult to decompile to return to the first source code. You ought to demand your engineer muddles the code with the goal that invert produced code is less coherent. It's imperative that you don't put any delicate things straightforwardly in you code (e.g. username, passwords) as they will effectively be found. This may influence the plan of your port iOS to Android application.
