Learning from ios and android together

If we want to learn about these two different mobile platforms at the same time, there are actually some "idle" Factors in it.

Compared with ios, android is exposed half a year earlier. At the very beginning, I learned the continuation of j2ee learning. I spent about a month watching videos and reading books. I had a basic understanding of android. I wanted to be a trainer for a small project. I didn't implement it for various reasons, so I put android on the edge.

Later, I bought a MacBook and started watching ios. When I first learned the basic syntax of Objective-C and the basic programming of ios, I spent about four days on it because the previous basics are okay, and then let go for various reasons.

These two learning experiences have given me a deeper understanding of the mobile development architecture. So last month, I started learning the two again.

When I set up the android Development Environment again, I was overwhelmed. I almost forgot what android is, it took a few days to look at the basic android getting started book from the beginning. However, the books on hand are really out of stock and cannot catch up with the times. This is intolerable for programmers who "blindly" pursue the newest like me. So I found the most fundamental document, android official document. Since I have not read these things well before, I started to translate official documents to read and learn English. It took a week to read and use various tools to translate several articles on the base. As a result, I re-established the architecture of android in my mind. (To be honest, android documents are too difficult to translate, mainly because they are easy to understand sentences without thinking about java, android document editors seem to be using various long sentences to show off their text capabilities, which makes non-native people like me very sad and sometimes speculate what the authors mean. But later I found that ios didn't have such a systematic structure document, so I would like to thank google for its kindness ). Later, I used a few demos with some of the new technologies I learned. I feel bored, and I began to learn ios again.

I wanted to use the same method to learn ios. After all, ios7 has changed much more than android. In addition, after Xcode5, the familiar things were lost. It turned out that learning ios memory management was a key point. Before Xcode5, You can manually choose whether to do the memory by yourself. Now, you must hand it over to Xcode, when you use release or something, an error is reported. Fortunately, I learned a lot about memory management before, or I cannot perform relevant tests now. (But from the perspective of development, these changes are good for a language or ios system. Such forced changes avoid fragmentation Like java)

Let's compare the development differences between the two:

1. Differences between development tools (IDE)

As an open-source system, android is the most famous open-source IDE-eclipse. As an almost omnipotent ide, eclipse also provides plug-ins similar to web development for android development. This allows developers to quickly switch to android development. Programmers who first developed android have never had the experience of creating an environment for android. On the weilai android official website, eclipse download for android is provided, which reduces the difficulty of starting android. In other words, google actually developed a new ide for android. I used it for a while, and the result was decisively abandoned. It is the official ide that is worse than javajan.

Ios uses its own Xcode at your own discretion, and ios development requires Xcode. At least I have not found any other. If eclipse is a modern ide, Xcode is more like a post-modern ide in some aspects. In addition, with the development of ios and Xcode, sometimes the code you write carries the shadows of some pseudocode, such as some syntax containing the keyword "@", which is like pseudo code. Xcode is worth mentioning that it does not let us pay attention to the XMl behind the View, but directly provides a page that everyone can understand. eclipse also provides the source code very professionally, as a result, many people started learning android by manually editing xml. In addition, Xcode introduces "connection" to associate code with graphics through connection, which is equivalent to MVC. It is a post-modern task that allows everyone to program.

I always think that the soul of eclipse is the pleasure of "Alt +/". In this regard, powerful tips are not available in Xcode, and the cross-platform nature of eclipse is also commendable.

2. Differences between java and Objective-C

Objective-C has a longer history. Java has abandoned the pointer concept, as well as its outstanding junk processing and memory management mechanisms, which are so commendable and easy to learn that it can become the most popular language in less than ten years. However, the attention and dedication of many people make it difficult to choose from various open-source frameworks on the Internet. In addition, the updates to this java version do not really discard some outdated packages or tool classes, making it difficult for beginners to differentiate when learning. In addition, the java maintainer has always lacked the courage to update a major version, which makes it difficult for developers to explain the pain points. As a result, the attention is gradually decreasing.

While Objective-C was born almost the same as C ++. However, few have heard of it a few years ago. Until the rise of the iphone, its attention quickly rose to the first three over c ++, only with java, C. However, Objective-C is so strange that it has some characteristics of ancient languages. [], @ is used as a special feature, perhaps to show its uniqueness. Without the help of Xcode, Objective-C development efficiency is much higher than VC. But in terms of language, it may not matter now, but Xcode's excellence makes us not just look at the language itself, but on the contrary, there are some uniqueness. After all, OC runs much faster than java, which is very important in the mobile development field.

3. Comparison of development documents and materials

After reading the ios documentation, you can understand the good intentions of the android development documentation. Compared with the android development documentation, I don't know where to start with ios. A part of the android document is obviously a good tutorial. It is better than some books available on the market. On the other hand, ios is a development document. If you have any questions, you can find out how to use it.

The network information is obviously not as rich as android.

In general, I personally prefer ios. Based on my love for beauty, I cannot believe that an ide can do this well. With the exception of the iphone, the feeling of being rich and handsome is reminiscent that ios developers are also rich and handsome. Based on this yearning, I am deeply impressed.