I agree with everyone's posts about the client end of ESignal is not very good. But Esignal could rectify alot of these problems by focusing all of their attention to the server side and letting third parites handle the client side.
However, Esignal decided a few years ago that many third party charting products were better than theirs so they decided they couldn't have that so they basically banned the ability to access their Esignal Standard APIs for any new products. They now only offer their decrepid Esignal Desktop API.
I tried to get access to them about a year ago. I was told they are now only available to corporate clients and not third party software products. They also told me that I had to submit a business plan with them so they could determine-in my opinion-whether my solution competed with their products.
So I have a some suggestions for Esignal:
1. Unbundle your data services and client charting packages. Offer your data services at a lower rate and then let the user decide which client they want to use.
2. Remove your restrictions on the standard Esignal API. This would allow more competition for new products on the client side.
3. Offer your APIs for more platforms, like Opentick does.
4. Stick to the server side providing fast, high quality data.
I'm sure i'll think of more later.
However, Esignal decided a few years ago that many third party charting products were better than theirs so they decided they couldn't have that so they basically banned the ability to access their Esignal Standard APIs for any new products. They now only offer their decrepid Esignal Desktop API.
I tried to get access to them about a year ago. I was told they are now only available to corporate clients and not third party software products. They also told me that I had to submit a business plan with them so they could determine-in my opinion-whether my solution competed with their products.
So I have a some suggestions for Esignal:
1. Unbundle your data services and client charting packages. Offer your data services at a lower rate and then let the user decide which client they want to use.
2. Remove your restrictions on the standard Esignal API. This would allow more competition for new products on the client side.
3. Offer your APIs for more platforms, like Opentick does.
4. Stick to the server side providing fast, high quality data.
I'm sure i'll think of more later.
I'm telling you man, god and I are tight like that. 