Some discussion about mobile development (in some cases, moving is a gimmick, and it is irresponsible to preach recklessly)

Some are talking to some of the company's colleagues about Mobile's understanding of the message. A bunch of words in the way

L

After long-term follow-up and information collection, I have some suggestions on the Windows Mobile side, I hope the company let me start this research and development. In the Company for Windows Research and development you are the most senior, so we exchange views, please from the technical point of view and Microsoft development, industry development point of view this idea is feasible? Thank you! For details, please see annex.

(Annex: Mobile Development proposal)

1. Objectives and Products

Developed with Windows localization program (based on. NET technology, WindowsPhone Technology) to implement a set of client framework to host the future of mobile ERP, mobile OA, mobile HR and a series of distinctive features of enterprise applications.

Just implement a set of client framework, the back-end service mode with the current unchanged, the same. For example, can be made on the flat sheet, you can fill in the library, you can make vouchers. Wait a minute.

2. Background and principle

The future is the future of mobile, but no back-end system can not be moved by the drag. We now have a basic background system framework. We have ESP, Smartweb, cloud technology to provide rich and powerful support behind the scenes. Now, at least technically, we can turn our attention to the device side.

At present, on the device side ocean, at a loss. Enterprise application How to move up, no conclusion, no one practice. Where did IOS, Andriod, and Windows get from? What will the future application form look like?

In the future, the device + cloud form is a certainty. The device can be a PC, can be a tablet, can be a mobile phone, or can be any kind of smart device, such as smart watch, smart home and so on. Too many forms, we only talk about enterprise applications.

In enterprise Applications , Apple has partnered with IBM to try to get him moving on the corporate side, but what about the two-mobile collaboration? I estimate the effect is optimistic, will generate this market, let users accept. It's a simple thing to believe that IBM is doing real enterprise applications, not mobile approvals.

Microsoft will be in the next two years unified mobile phone, tablet, computer operating experience, at least at the development level, the unified three sets of system API as a set. In the future, even at the moment, the development of WindowsPhone is almost consistent with the development of Windows desktop programs. So, in Microsoft's world, can not be very divided between desktop programs and mobile programs. And the real enterprise application, will be in "tablet computer" such equipment on the force.

processing power and power consumption with the release of Intel's new mobile chip, Microsoft Windows-based devices will be thinner and lighter, and the longer the standby time, the better it can be for a full day of work. And these Intel chip-based devices will have half of the complete PC architecture of the device. What does the full PC architecture mean? You can run Win8, and there are so many applications that you can do on a PC, and now you can do it on a tablet.

So, in the end when the enterprise mobile outbreak, I think it depends on the chip trader's efforts and the efforts of the OS vendors. For the next two years, the solution to Intel's processing power and power consumption is inevitable.

I've been tracking these applications for over two years, and I'm sure Microsoft will eventually make a contribution to enterprise mobile applications. This is determined by its genetic and technical barriers. Even if Apple +IBM success, but it is not a single big, and the industry also half of the voice that the gene and blocking iOS is not suitable for hosting enterprise applications.

Microsoft seems to have a problem at the moment, but precisely because of this, it needs to cut into the advantage of gaining time.

3. Propulsion and landing

L Required Personnel:

. NET Programmer two (C # language), this talent is more than the development of the iOS people more easy to find. Now I think that. NET has the opportunity on the mobile side, on the server must be no chance (occupied by Java).

L Required Equipment:

Windows Tablet PC.

L The required development environment:

Widnows8 +. NET development environment. Now we have a notebook to go with.

L How to land:

As I said earlier, in the Microsoft platform, the future is not very mobile and desktop. Mobile apps involve UI, communications, hardware interfaces (such as various USB custom devices).

Referring to USB custom devices, I think this is the absolute advantage of Windows tablet. Flat is not the light used to approve the list, it can take a casual walk, in the dock, plant, warehouses, airports, supermarkets, oil and so almost all the environment. In these environments, I want our Windows programs running on tablets to perceive, capture, and enter the digital information needed for these scenarios through a variety of USB custom devices. This, must have a USB interface. How to use a good tablet, it must be more from the hardware to consider, simple software or in the computer, is not possible.

In addition, we can also guarantee to develop a set of such clients, can adapt to the company's current multi-backend architecture. Specification of call specifications for unified device-to-backend services I've mentioned it many times and can be achieved.

4. Summarize

The company will face development and change in the next few years, there are opportunities and challenges. As a shareholder, I very much hope that the company has a new bright spot, there are new products to appear. Time waits for no one, we need to race against time, to avoid unreasonable decision-making time mistake, must at the right time, let the right person to do the right thing. This article says that the development of windows in this area is still a zero at the company. But I've been tracking it for two years, unless the Microsoft Windows system dies on the mobile side, and it's bound to succeed.

----------------------------

ME: Hello!

1, I am not very much in favor of the future move will be very big as this point of view, as far as we serve the customer, mobile application scenario is still relatively small. Do it can only play a propaganda effect.

2, Microsoft on the mobile side will have a great prospect, this can have.

Put down the above two points of views do not say, a few comments, a total discussion.

1, is the use of local language or Web development

I tend to develop web pages. There are 2 reasons: one is that the Web page can be compatible with all mobile devices. Second, with the development of Web page technology, the difficulty of Web page design is less, the way and effect is more and more beautiful and rich. Third, if you do local words, different platforms need different technology and personnel, for Puling is a waste, especially in the current situation of human tension.

Pure Web Development, 1 is platform compatibility and browser compatibility, 2 is to access local resources security issues, such as access to local devices, files and so on. Compatibility is a workload, and access to local devices may require the development of plug-ins for different platforms. This requires comparing the cost of dealing with these issues with the cost of the target mobile device localization development effort. If the cost of the former is greater than the latter, consider localized development.

A compromise solution is to develop a shell, embed Web pages internally, and access local resources externally.

2, localized client framework development. It is necessary to "implement the client framework" If you are using localized development. But it is not recommended to do the interface designer, only the structure of the framework, the provision of development patterns and standards, interface and non-interface components are OK. Interface Designer We do not have this skill, do not do well, will greatly affect the development efficiency.

I do not know much about mobile development, for reference only, so the above comments may not be of great help to you, moreover, in the overall technical line of the company, you have more than I have a holistic view. In fact, the company is not the question of what to do, but how to do the problem.

===============================

L: Why is it that I am too optimistic about the difference in opinion? I think the following points are worth considering:

1, if there is a mobile PC, such as Surface Pro, such as the support of the device, the real mobile application can be carried out, not only the approval class, a variety of scenarios can be used, it will be a different world now.

2, on the tablet, on the phone, I think the native application experience is better. And my idea is to control all kinds of external devices on the device side, and realize some of the underlying functions that the web can't do. Releasing the energy of the device requires a localization program. The web's way of making a fool of Can, as a strategic development, should be based on the primary.

3, although facing multiple platforms, but I am very concerned about the Windows platform, iOS or andriod may not be able to carry this responsibility.

4, certainly do not do the designer, the client is only responsible for displaying the defined component-level package. I object to ESP, which is the design of the designer, the effect is counterproductive. Do not leave room for programmers, how does the application do well?

5, about the manpower, I said 2 people really is also can, backstage have, the middle layer of data exchange have, we just put smartweb realization replaced with. NET native implementation, with JS can be achieved, with. NET certainly can be achieved, but also to read the hardware device layer of functionality. The architecture will not be redesigned and the service will not be re-developed. This was a good time to design the overall framework of the smartweb.

I feel that the enterprise mobile application is coming, this is not a simple approval of a list of this, but a variety of scenarios. Many require Surface Pro external USB custom devices to be implemented. The industry can appear Interl architecture Surfacpro is a gospel, hope more manufacturers can follow up, launch Interl+windows tablet. Many people talk about mobile must ipad,andriod, I see not them, but windows.

Hope to continue to explore each other.

=============================

ME: A little busy, reply a sentence.

1, if you think surface is a mobile device, what is the difference between this device and the PC in addition to being a little portable? Microsoft's definition of surface is a super-polar book that can occasionally be used as a tablet. There's no difference between developing a system on surface and a PC, so what does mobile development say?

2, if you consider a more portable (smaller screen) Windows device, who will use it to record a list, do more complex interactions, or a consumer platform, rather than a productivity platform?

I have always believed that in the production field, mobile applications are more gimmicks, like the current central plains to customers to develop mobile conferencing system, each attendee holding the ipad to see the document, vote, this is not a wonderful? But the consumption domain is different, the audience is not different, the demand is different, does not have the comparability.

3, designers do not do very wisely, and Microsoft's IDE to compare, any company's so-called IDE is slag.

Personal opinion, a total discussion.

========================

ME: Hello!

System on the line, the third day, finally stabilized, continue.

1, in fact, there is no prospect of mobile applications, specifically, what can be said in the mobile field, the key is to see our service customers, our project has no this demand. This simple, you can put all the company's products, projects, customers over again, to see the nature of the system we do, we can draw a conclusion. My understanding, our customer service, enterprise customers, the development of the system is also an enterprise information management system, but also are operating management category, and did not extend to the production line. The target group of this kind of system is the Office family, the Office place is unchanged, they have little need of mobile office (at most in the office to deal with the unfinished business, go home overtime processing, such as vouchers), their work content is very single, are repetitive transactional work. This kind of transactional work, need is big screen, fast input, efficient human-computer interaction, the higher layer, may be the leadership, they are concerned about the report, graphics, business approval, only they have a little mobile demand, leadership busy, often in the outside, there are cool needs. And that's what we're doing. If this is the only word, the target group is much less, and there is no need to spend more.

However, we are now doing the public service charge for this project in the future there may be mobile demand: mobile phone payment. But this is already very mature, and it is not our main business.

2, you can say that the user has no demand, we guide them. The process of enterprise informatization, I understand is, strategic consulting and planning-generating business requirements-technology development, which is from the top to the next chain, our position of the first business requirements of the lower end and technology development, up to a half of the process. Every system we do, almost every one of them is a request from the customer, from the technical environment, the development language, the location of the button, the naming of the menu and so on. What we lack is the first step, strategic consulting and planning, that is, the source of demand, how do you lead them on the move, how can you use the technology to pry the upstream demand?

In a word, in our business field, I can not think of what mobile development has to do, of course, it may be that we think of, have experienced. It's a good way to do an internal investigation in a company.

In fact, there are many places that can be done, except for this.

Opinion, for reference only.

==========================

L: Thank you for your busy thinking!

As you say, moving this thing, what we do now is basically a kind of embellishment, the cost of leading is too big. So from this point of view, there is really nothing worth doing.

But somewhere, I feel that the real mobile business era is coming, and this era is likely to be based on tablet applications, in fact, it is Microsoft's goal. So, I only mentioned Microsoft's flat-panel solution, but not eager to do, but also wait and see.

Microsoft gives a solution to a tablet-desktop, or a desktop system that can be moved. I think this is an important direction for the future.

Because our company does all is the enterprise management Information System, basically is for the person who sits in the office the body uses. From this point of view, Mobile is always a kind of embellishment, at most, mobile approval, this point of view, two years ago I also expressed this, also to X said, he is not happy boss. Now I also think that mis such systems are not necessary to move.

can we jump out of our service customers to consider, such as supply chain systems, ERP system, can we dare to shout out "mobile ERP" or "Mobile xxx" goal? Is there any new field we can do? For example:

1 : such as mobile HR, inside the recruitment interview function, so that our experts do not have to run the scene, but by the HR small secret to the scene on the line, you can remotely through the video to interview.

2 : Mobile Supply Chain, I think this is a recent business away from us. Collect, send, transport, move up will be more cool.

As far as I am concerned, it is in fact waiting for Microsoft to make a difference in this field, if Microsoft does not do well, maybe others will do well. I still attach great importance to Microsoft's ability.