Personal experience in iOS and Android Development

Proud apple, selling cute android.

From the perspective of personal psychology, Android's little robot is fascinating,

A bite of Apple pays more attention to design and is simple and exquisite.

If there are two systems, I think it's better to buy more Android systems ~

The robot looks better, Apple =.

Recently, the second version of the company's Android product has reached the final stage. I have added several functional modules, and I have basically made several interesting modules.

Then the IOS version reached the final stage. In terms of computing, from the planning of the year June to the end of the year September, the progress was average or slow in terms of time periods.

However, the product itself is a continuous feature, and the version of the iOS platform is directly synchronized with the version of the Android platform. For some new features in phase 2, the new interfaces of the client and the server are added,

Therefore, some testing causes also take a long time.

Another point is that the company does not have any colleagues in visual design or specialized UI. The application model and interface design are basically the same. If you look at other people's products, you think that the AAPP interface is well designed,

What is the humanization of the Interaction Design of BAPP? Can we consider adding this feature of Capp?

This will lead to a new version that we thought was coming to an end, and because we were about to modify the UI and interaction logic, a new small function was added. (I will tell you that our Android version will be launched in 3 or 4 months,

It's half a year since now ~ This second version lasts a little longer ).

Therefore, it is sometimes felt that a good visual design and Interaction Designer not only improves your product experience, but also shortens the development period.

I. Knowledge of iOS development and Android Development

Android: it is easy to get started and turn around. In the current industry, both salary and employment are good, and mobile Internet is still telling development.

The Internet is a society with more passion, more miracles, and more bubbles. Simply put, I first mixed up to eat, because I ran to the food market with the ideal, and saw that the pork ribs cost 20-23 yuan a pound.

IOS: in fact, most of them have been transformed. On the one hand, they think things are less expensive (although IOS developers are growing rapidly now, but a few months ago, the company was looking for someone to flip their resumes,

30: 1 ratio ~~ Non-official objective proportions, subjective factors will also be taken into account when applying for a resume). However, the competition for iOS development is relatively gentle, and the salary will be better than that for Android users;

Another point is that iOS development is cool?
Most people think that iOS development is a little more powerful than Android development. (Let's take a look at it. Some people think that iMac for iOS development is so cool that Apple is a good product,
However, when it is really good for you to talk about it, it is also about people and cloud, design, artistic sense, and so on. Of course, this is also true. Android has become a plug-in product by the media due to various shanzhai,
Of course, I would rather think this is a self-mocking culture .)

Individual: Android was around 1-2 years old, and then I went to learn iOS, because of the company's environment and status. Some people say, Why are you switching to iOS? It's a traitor, a hacker ~

On the one hand, you may want to get in touch with multi-platform development, and on the other hand, it may be a period of sudden weakness. During the weak development period, I suddenly felt that I had grown slowly, and then I felt a little lacking in passion.

Indeed, Android Application Layer development often enters this strange circle, and our company's products are relatively simple. After basic development, there will be various adaptation, partner merchant version modification, and O & M.

The company is ready to develop its own iOS platform, and there is no one. I'm so excited. (well, I'm not so excited. I'm premeditated ). After all, learning to develop multiple platforms is not a bad thing,

You can understand the differences and commonalities between the operating habits of the two platforms and learn from them. I think it is better to develop a complete new project than to maintain it.

Ii. issues during iOS and Android Development

1. user habits

Although they are all mobile phones, they also have a great deal of experience in operating habits and subtle UI habits.

What is more tragic is that, in general sense, the application is transplanted from IOS to Android, and our company has just switched over ~

The simplest interface framework is the change of the back interaction, but later I found that some gesture editing and user identification logic without text buttons were found.

If we just port Android, because Android itself provides a wide range of space domains due to the screen relationship, the interactive buttons can be displayed.

The layout is on the screen. However, for iOS, I think, is my fingers too thick? Button-intensive, it is definitely a visual effect, and the operation effect is hard to hurt.

Therefore, many operating habits inherited by default in the IOS system will be introduced, such as the deletion of gesture buttons, text-less and edit of various menus and info buttons (add, delete, modify, and delete) the default logical process of the operation.

2. Adaptation

This is actually nothing to say, but I personally think that screen adaptation is not a problem. After all, there are several screen sizes for Android, and there are some models and hardware adaptation problems,

It is a tragedy to run into a number of fake hosts that have never been cool.

IOS screen image resource adaptation is much easier.

Then, considering the compatibility of the SDK version, Apple also provides some classes for judging the version compatibility. In most applications, the latest SDK is used for development,

However, it is basically backward compatible, because there are not many applications that use new features.

3. Programming Language Style

I think the two are okay. Generally, application-level apps basically use a layer of language, and then OC is used to it. In fact, it feels similar to Java.

IOS uses some basic C-language code, such as macros.

It is difficult to get started with a language. I think Java has been used for a long time,

IOS has slightly changed the language writing specifications because it is oC, but this is not a problem. The only thing that comes together is API proficiency.

That is to say, I think Android is a little simpler. Simple cause 1: There are a lot of materials, translation is also mature, open source code, and API code structure is also acceptable.

Have a perceptual knowledge. Compared with iOS, the materials are still acceptable, but they are relatively simple. The basic purchase of SDK books or tutorials is just a learning process. If you want to study in depth, you can only go on your own.

Refer to the official English API.

Iii. Simple Description

When I was learning iOS, some friends always said that after more than a year of Android, you did not do it? If I say this, I am tired of using application-layer applications. Someone may say it with contempt:

You can study the framework layer, bottom layer, and ndk development.

First of all, I just want to learn iOS, instead of switching to IOS ~ For Android, the water is really deep, but you need to consider your work environment and situation.

Many times, the success of deep learning and getting into touch with a new or deep thing requires the development of an external environment. For example, I have a friend who doesn't want to make system customization due to work relations,

I originally said that I would like to learn about the framework. This is just to provide him with a breeding environment. Although it took him one week to change a system module in the past, then,

Now, it's no big deal to compile the source code, customize launch, and add new modules.

I have been in touch with the application layer, so I can only talk about it when I go to the next ndk. I can only say, "Nobody, I am familiar with the environment, and then I ran through helloword ".

I think IOS is more of an experience-based process. To be honest, Apple's system is too closed. It only provides documents and interfaces for you to call,

This is like giving you a car, a usage instructions, you don't know. This also has advantages and disadvantages. What is undeniable is uniformity and conciseness.

The disadvantage is that when I jump to the SDK source code During Android programming, IOS suddenly wants to see an internal implementation of a class and finds that there is no way to jump ~

Therefore, it has recently been found that, for pure encoding and code reading, Android is more fun.

For the final product, the benevolent wise sees wisdom.

However, in terms of products, both practice and experience are required.

Of course, as mentioned above, I mean, maybe IOS requires more time and Android will focus on in-depth research.

The above is my personal experience.

When I was doing Android, I could not help but have fun reading the source code and other in-depth understandings: Oh, it turns out like this.

In iOS, the fun may be more reflected in the visual and operational aspects when the app starts to run: Oh, good, the Industrial and Labor applications are really cool (of course, if you have a good visual or artist ).