URLs and browsers slowly disappearing from the foreground

Article Description: apps and Icloud:url and browsers will fade away from the front desk.

The technical details of ICloud are still under the protection of NDA. But everyone's curiosity cannot wait until NDA expires and then satisfies. This article is based on the iCloud of speculation written, reliable or not, waiting time test.

Complexity and simplification

Find a notebook, start ...

Open the browser, well, today with Safari, Chrome, IE or Firefox?

Input twiter.com, ah, no, it's twitter.com.

Look at the page load of the beacon wheel hair for a while to stay ...

I can finally enter it! What am I going to say here?

What if you use the IPad? The above steps change: Pick up the iPad and light it. Click to open the APP. Input!

Path

Twitter is also supporting both of these approaches, and then the founders are even more simply.

Path directly discards the browser. In addition to Flipboard, Colors⋯⋯ can foresee that this list will grow longer.

The slides themselves in this section can reflect the simplicity of this scenario. Users benefit more from it, and the App is easier to make a good experience on a mobile device than in a feature. Moreover, Web services are completely hidden behind the App. Path.com or paht.com? No need to care anymore.

The App?

What is APP?

Apple gave us the best explanation with an ad: " There's App for".

App is not the difference between software and hardware (MS prefers the word "software"), and the nature of the app is a solution to the situation.

Today, the use of network services to solve problems of the way of thinking, has infiltrated our blood. In a room, I would not use the card reader to copy files to friends. I will Upload to Google Doc, and then Share to him.

Path is the case. The IPhone, the Path App and the Web services behind it are one. No one can use this solution when we want to "share photos". For Path, the technical layering should not be exposed to the user. The key is to integrate possible technologies and better solve real problems for users.

At this point, the hardware, software and cloud services are the sum of the three, in fact, is the Path App. (Yes, it also includes hardware, the Path experience is limited to the iphone's screen and the iphone's camera)

Icloud

Apple is a master of soft and hard integration. While the soft, hard and cloud integration of the advantages of the three, he should not be overlooked.

But once again, Apple was different: instead of making a PaaS, he offered a relatively simple cloud storage service. But a simple cloud storage is also significant: Apple devices such as the IPhone, IPad and Mac get through. IOS and MacOS can also be connected by ICloud.

And, from a developer's point of view, ICloud is a very natural evolution. In the applications directory of IOS, each App has its own folder to store private data. Let's say IBooks will put the downloaded book in there. The question is: What if you buy another iPad? The IPad's Applications/ibooks directory does not have the book.

Google may write a Web service, put the books up, give each person an account, save progress. ICloud is a natural extension of the IOS private folder: Find a Web server where you can save private data to the APP.

In the IOS app, the app saves some data with just one line of code:

[[Nsuserdefaults Standarduserdefaults] setobject:obj forkey:@ "Userinput"];

Since ICloud is a cloud folder for app service, the app Upload something to ICloud, and it could be a line of code. For IOS developers, this is a very cordial and natural way of using cloud services. (PaaS?) The server-side language and framework must be learned from scratch. ）

The new cloud development framework

ICloud alone is a cloud storage service. But by merging Apple's Hardware (IPhone, IPad, Mac) + Apple software (Apps, IOS, mac OS) + ICloud, you'll find that he's subverting today's popular browser development framework.

The new approach can also span both IOS and MacOS platforms. Moreover, development is faster, simpler and more experienced.

Browser application?

However, browser-based applications are also evolving rapidly. In Ajax, the data, logic, and UI begin to shift to the client. HTML5 further enhances the browser capabilities. Comparing browser apps with ICloud apps, the difference between the two is little. Later, I'm afraid it will be more and more like.

Moreover, at present ICloud seems to lack server-side logic (language and database), he can solve the data exchange between different Apple devices, but it is unlikely to easily link up a large number of Apple users . Like Twiiter a large number of data-related services between users, ICloud is difficult to handle.

Fusion

Today, Safari has access to data on the IPhone's GPS and gravity sensors. On the other hand, UIWebView is also widely used in apps. Perhaps not long after, the difference between network application and Apps, is already not the ordinary user can distinguish.

In fact, the browser application is also: the scenario and the use of the solution. Apple saw this earlier than you and me. Evidence? Is the launch of the already long Add to home screen.

Last Words

So it seems that there are two things that will slowly disappear from the foreground: URLs and browsers themselves.

And no matter how the technology changes, the solution from the user does not die.

–

Ps. A ride is advertised, IFANR enabled the Google +1 button, click it, thank you!

Source: http://www.ifanr.com/42932