forum.e-valid.com

How would you position eValid technology relative to other offerings. Including open source and the stuff from the "big three" [you know who I mean]?

silvern wrote:How would you position eValid technology relative to other offerings. Including open source and the stuff from the "big three" [you know who I mean]?

Thanks for asking, and that is a difficult question to answer, but it is a fair question to ask. So let's see if we can give you something of an answer.

For one thing, the eValid approach -- to put all of the test functionality inside a fully functional web browser -- appears to be a unique idea. As far as we know, none of the other "big three" has done this.

We've often asked ourselves, why wouldn't the "big three" implement this simple and powerful approach and we don't have any easy answer. Most people who we discuss this with, and who are familiar with the "big three" offerings, suggest that it is a combination of "corporate momentum" and the desire to not simplify their solutions as a way to preserve revenue (or to prevent revenue loss).

Yet, here is eValid, fully operational and entirely contained in a browser, and unique in this approach to testing web applications.

Who knows what the future will bring?

eValid Support Team

eValid wrote:

silvern wrote:How would you position eValid technology relative to other offerings. Including open source and the stuff from the "big three" [you know who I mean]?

Thanks for asking, and that is a difficult question to answer, but it is a fair question to ask. So let's see if we can give you something of an answer.

For one thing, the eValid approach -- to put all of the test functionality inside a fully functional web browser -- appears to be a unique idea. As far as we know, none of the other "big three" has done this.

We've often asked ourselves, why wouldn't the "big three" implement this simple and powerful approach and we don't have any easy answer. Most people who we discuss this with, and who are familiar with the "big three" offerings, suggest that it is a combination of "corporate momentum" and the desire to not simplify their solutions as a way to preserve revenue (or to prevent revenue loss).

Yet, here is eValid, fully operational and entirely contained in a browser, and unique in this approach to testing web applications.

Who knows what the future will bring?

eValid Support Team

So, OK, given that eValid has taken the high road by building its test engine inside a browser, but there must be some reason why the "big three" have been avoiding doing that? Is it too hard? It's hard to believe the "big three" would shy away from something that is hard to do? Or is it something else? Maybe it's too simple and obvious? Or do you think that every contractor like me has a vested interest in doing things slowly to build up billable hours rather than doing things efficiently to get the job cone? WTG