Transition from PC client to wireless client

It has been almost a year since I got started with Wireless Development. I hope it will be useful to you :)

1. Why do I need to go to the wireless client?

One is work needs, and the other is always interested in wireless. I used to write something simple.

Demo for fun :), the arrival of 3G, I imagine that I should switch from PC Client development to wireless client development.

Many companies are hiring, wireless is an unlimited prospect for our developers, and many opportunities are waiting.

With us. (Which of my friends has Wireless Development Experience (WM, Symbian C ++, j2's, and iPhone )?

For work, you can leave me a message or send a message. Here, we will make an advertisement :))

2. What are the difficulties in transferring to wireless client development?

From my own one-year transformation process, I feel like:

1. The initial difficulty is, of course, the establishment of the development environment.

2. Learn how to debug and joint debugging of real machines

3. Documents on every platform are incomplete. You need to explore many things.

4. network processing (cmnet, cmwap, and WiFi)

5. Model adaptation (I personally think WM adaptation is easier)

3. Which platform is the fastest getting started for so many platforms?

I am a Windows development engineer. I personally feel that windows to Windows Mobile is the easiest

Microsoft has provided me with such a good ide. The simulator and the real machine are basically the same, especially the joint debugging and comparison of the real machine.

Convenience. I feel too complicated for the s60 platform of Symbian, and the developer's threshold is too high.

There are too many western regions and the signature logic is too complicated. I talked to an outsourcing company a few days ago. They have been doing this for so many years.

With the development of Symbian, few people in the company are familiar with signatures! I personally prefer WM.

The Shanzhai is like WM! The second step is the iPhone environment. If there is no mac machine, you need to create an environment.

If you are a WindowsProgramWe recommend that you start Windows Mobile first ".

4. There are various OS types on mobile phones, which are a headache for developer adaptation, especially the UI. There is a unified solution.

?
It is really easy to make a model, it is difficult to adapt to different models of different screens, WM a setCode,

The s60 code, the iPhone code, and the Java code are difficult to maintain.

This topic has been discussed for a long time, and many companies have seen it. The basic idea is self-built.

I have made a simple XML Parser for the client, and each company defines a set of labels.

Some complicated work to help others do well. It is faster to create a new application. You only need to write XML and configure the UI.

These companies are also getting started, basically the products are not very mature, after all, their own defined labels are limited, each

User needs are different, and a process is required, which is similar to using the browser kernel for parser customization.

The interface is the same, but in the past two years, browsers on mobile phones support the entire browser, and it feels more reliable to use it directly,

In the past two years, I have also raised some comments about Widgets. The most famous is Yahoo! Widget, I read its source code

Its kernel is rendered based on the WebKit browser kernel, and some special effects are added to it.

It looks pretty cool. My final view is that the transition from a pure client to an interface over the past two years is indispensable.

For companies that want to cover more users, the best example is QQ.
We used to develop PC clients. We often use IE's browser as the interface engine and customer.

The Flash client is familiar with and has tried to use flash as the interface engine. However, the problem with Flash is that every user machine

The version is inconsistent, and Flash is not installed on many machines by default.

 

The arrival of 3G is also an opportunity for our developers, and a group of heroes have emerged!