Re: The End of the Web? Don’t Bet on It. Here’s Why

Sridharan_Srinivasan — Tue, 20 Dec 2011 12:43:31 -0000

My 2 cents observation are that for Consumers (Native App or Hybrid App is better) because the User Experience is Push Type where using a Browser to access an App is Pull Type which sucks. But for the Paymaster, it does not make sense to build multiple app for each Mobile Platform.

Only a Native App can allow me to give a snapshot of my data in the cloud without me doing anything. I don't want to login to Gmail to know how many unread mails i have or when a important mail has been replied.

I am not sure why no one has ever thought of putting a embedded web server inside a Native Framework (similar to Phone Gap but capable of Web Server Code - www.arshu.com) so that you can use the same code deployed in a Server, deployed in Mobile Native Framework and which every way the future moves, it will not lead to wasted effort.

Why is it necessary to bifurcate development, why not take both the approaches and based on the Application requirements, decide the most cost effective and most user friendly approach which solves the Problem.

Re: The Mixable Web (1)

Sridharan_Srinivasan — Sat, 12 Sep 2009 14:39:33 -0000

Your concepts and your blog information are awesome.

I have been working / researching during my free time on something like this where applications can be built from components. My hypothesis was to test whether assembly separated/distinct from coding of an application leads to reduced complexity/increased flexibility since my focus was on reducing my pain and customer pain in executing large enterprise application developments.

But my approach was more generic in that I don’t have any basic components, what I did was abstract the connections of the components as a language of assembly and hence built a generic framework which in theory can assemble any components using a simple generic language of assembly.

I found that my language of assembly consists of 4 simple metadata, namely, specifying a context, adding components into the context, configuring components into the context and linking components into the context which can lead in theory to assembly oriented application development.

I created a proof of concept web site which was fully assembled from standalone components which helped me to prove it can works, but still need to test it on complex data driven applications or even use it as you are doing to accept data from multiple streams.

I am currently in the process of testing in a limited way whether it can used to develop a proof of concept for a large enterprise application for the architecture industry which I am currently developing for a client.

If you have time and can check my proof of concept website www.arshu.com on my approach to solving the complexity/flexibility of web application and give me your comments, i will be greatfull.

Disqus - Latest Comments for Sridharan_Srinivasan

Re: The End of the Web? Don’t Bet on It. Here’s Why

Re: The Mixable Web (1)