Home

Let me give you a quick introduction of Ultimate Mobile Pro. And explain why you should have this tool in your project if you are targeting mobile development with Unity.

What the Ultimate Mobile is?

This is a bundle that contains Stan's Assets best mobile native plugins inside wrapped with powerful unified API. The goal for the product is to cover all your native feature needs for Mobile development with Unity.

Despite the cross-platfrom API, you can also use all the features of the included plugins:

• IOS Native Pro
• Android Native Pro

If you would miss something, never hesitate to get in touch with us. We are always happy to accept reasonable feature requests. Supported platforms, services, and the number of features will continuously grow.

Get from The Asset Store | Scripting Reference | Forum | Support

Ultimate Mobile Cross-Platform API Benefits

• Codes can be reused. Instead of writing fresh codes for every platform, reuse the same code across all platforms.
• Editor Testing. The Ultimate Mobile plugin will emulate native services behavior when running inside Unity Editor. No need to use a real device just for the implementation tests.
• Unified Services. Plugin not only provides cross-platfrom API for mobile native service, but also it contains a unified API for the most popular plugins. For example, you can implement an advertisement with Ultimate Mobile and then choose the plugin that will serve the advertisement.
• Controls Cost. No longer need to spend on developing apps for every individual platform separately.
• Sameness and Uniformity. Using cross-platform app development ensures that the overall look of the app can be maintained across all platforms since the same set of codes are being utilized.

Under the hood.

We've been working with native services for quite a while, and as you may expect, each platform has its own "know issues" and "not really obvious flows/workarounds"  you need to know when you want to make a robust native service implementation.  Let me give you an example. Let's say you want your user to sign in with the Google Play. Here are some items you should know:

• The difference between interactive & silent sign in.
• The difference between a user account and a user player objects.
• All the flows how a user can switch account or sign out without using UI provided by your game.
• What is going to happen if the user will press the home button during Sign In process and activity will be killed by a system.
• How to react to Google Sing in Errors (documented & not documented) and how to implement error resolution flows if possible.

After working with iOS/Android for the last couple of years, and constantly getting customer reports, who use our products in huge projects, I can keep going all day describing small but important things that you should know about native implementation and flows you should handle. And this is precisely the case Ultimate Mobile designed for; it will get all this work off your shoulders.  

Pro-line principles

Apart from all the statements above, the Ultimate Mobile will inherit all the pro-line plugins development principles:

• Full Open source. I believe only open-source products can work for the developer community. If you are a junior developer, we will be happy if you learn something with our code. If you are a senior developer, we do not want you to have a “backbox” in your project, and we are always open to critics and suggestions.
• Strict code convention. We mostly use default the default C# Coding Conventions, but with few adjustments, we believe would help our users.
  • Filename / Class will contain plugin code prefix, so you will always know where it belongs.
  • Every public API is documented. Check our the Scripting References.
• Nice looking and user-friendly settings editor. Every plugin we make will have one centralized, good-looking, and intuitive settings editor.
• Ability to enable/disable modules. We understand you want to keep your project as clean as possible and application build size as small as possible. With our plugin only feature you use will be included in the project. You also have to enable explicitly enable the module, so you always aware of what exactly included in the build.
• Automatic project configuration. You do not have to make any additional configuration for your build. If something is missing, the plugin will fix this with the build pre-processing stage. The main goal is to be able to support cloud build services out of the box.