Websockets Return on Investment (ROI) (Part 2)

I was expecting more criticism for the generalized call that was made in part 1 of our ROI for real-time web projects. Because it sure is possible to measure certain parameters when you want to future-proof your web projects.
Below I will show you some important things to consider when starting a realtime web project, regarding your return on your investment.

The first thing to do

The first thing you should consider is the selection of developers. Many call themselves web developers, but far from any guarantee that your application is designed for the future. Responsive design is easy to check off but what about the database, code-language and choice of hoosting partner? Beautiful and cool is not equal functional

The Second thing

The second thing you should take into consideration are: do the developers work with standardized frameworks? For you as a client, this is vital. What happens if you want to re-place the web producer in the middle of the project and no one can continue with the work they started?!

The Third thing

The third thing you must do is to read about the different options that are out there. If your manufacturer chooses a framework that requires 2000 lines of code to run your application in realtime when there is others that can be implemented with only 25 rows and performs the same function as the first.
Why shell you pay for the time that the extra 1975 rows takes to write?

Entire systems

For those who want to upgrade their internal systems, I would like to point out difference between choosing a framework that is self hosted over cloud-based services. Do you really want to send data out of your system and back just to increase speed, when you can get better performance while retaining all the data inside your firewalls?! I guess not.
Or like Phil Leggetter - Real-Time Web Software and Technology Evangelist says in his tweet October 26, 2012:

If you're looking for a .NET self-hosted solution then XSockets, SuperWebSockets & Alchemy are options. 

At last

The last thing you should consider is the proof of concept. Have your web agency done anything like this before? Or are YOU their proof of concept?
Today there are a lot of applications that are only created just for proof of concept. The market is so young. And then the side effect of a variety of applications which only serves to show what can be technically.
You want the customer benefit. You want to make money from your application.
Ensure that this is the case!

Websockets Return on Investment (ROI) (Part 1)

The classic ROI model is one of several parameters that purchasers uses when choosing which team to create the "new" web app  for the company. Obviously, the status, qualifications, price, etc. is also included in the discussion, which all suppliers are used to relate to. But how do we measure an investment in real-time technology?!

In the simplest cases, such as casino and gaming sites, increase loading speed with 20% and it will be equal to 20% more gaming on the site. The less the user needs to wait, the more time he has to keep on playing.
In other cases, such as financial markets, rapid decision is a must to do great business. Milliseconds can be translated into millions of dollars - plus or minus - depending on whether you are number one or number two to buy or sell. Here, it becomes obvious that new technologies like WebSockets fills an important function in the future.
But how do you describe the ROI for a government agency that wants to make its intranet smoother? Or a major newspaper who want to make their digital editions more attractive in tough competition with other newspapers?
Or the example of the small shop just around the corner that has just opened an e-commerce with a minimal budget?

I say: Forget ROI, because you have no alternative?

Your customer is already there. They are aware, they does not like to wait, and they are very used to getting what they wants - exactly when they wants it.
Studies show that even at a half-second waiting time for loading webpages results in losing the visitors. And lost visitor is lost revenue. Depending on half a second!
Or as the slightly ironic comparison that Scott Gilbertson does with Google's developers that states that you lose customers already at 250 millisecond latency. (Most likely an exaggeration if we think beyond real-time games and real-time control via the device)
You will not be able to measure how fast you earn back your investment in real-time technology by getting more visitors. Your sites content and your marketing actions will determine whether you get new visitors or not. Real-time technology will help you keep them!
The same principle prevails in all segments. Your users are learning to make demands on speed. We are daily fed with advertising that says "select us as the supplier for your internet connection - we provide xxx mbit to you!
Your customers take for granted that you will deliver this experience. The've paid for the fast connection ... (they do not realize that your not in charge of the lines)

So what do we do?

So in the case of the State agency that operates a web-based intranet: Upgrade to realtime communication within the network so that your employees do not experience your working tools as a problem. Though they expect them selfs to surf at lightning speed.

You who drives the big newspaper: Besides web optimizing your material in size and shape you need to ensure the download time to your mobile newspaper readers.
We are born all the time with information from all directions, so when we have chosen to look for it - then we do not want to wait! (Especially for heavy ads from your advertisers)
For the little shop on the corner, I just want to say: Can you afford to lose a single customer because they can not bear to wait?
An obvious answer would probably be "no, nor can I afford to pay extra for a real-time web functions on my site..."
But here is the little store wrong. For it is no longer very expensive to implement real-time functions in your web sites. It just depends on which provider you choose (which we will cover in another article)

Anyway, the conclusion is quite simple:

What are our alterntiv to future-proof our web sites now that our customers are so spoiled?

 None.