Growing a SaaS: Avoid Confusing Dual Offers
whalepages.com
whalepages.com
For those curious about the technical specifics of our two offerings, we had (and still have) both a hybrid proxy/broker system and a basic JSON messaging system. The proxy system is the reason we started the company. However, we built the JSON system so we could compete directly with companies like Pusher and PubNub.
In old versions of our websites, we tended to highlight the JSON system over the other. For example, in 2014, the "Simple" category was promoted first: https://web.archive.org/web/20140207193606/https://fanout.io...
In 2015, we changed it use a left/right flow. However, the proxy system was still branded as advanced: https://web.archive.org/web/20150315032351/https://fanout.io...
Today, the proxy system is the only one we promote on the site. In order to reach that point, we had to figure out how to make the proxy system more usable. We've succeeded at this by creating very fancy integration libraries, such as our Django library: https://docs.fanout.io/docs/django-quickstart
I believe that is a great model for smaller SaaS companies to follow, as it reduces a lot of the risks ("use our service to reduce your time to market. If you don't like it later on, here's your out."). Great stuff!
When I'm on the buyer side, often one of my top concerns is understanding how I could potentially stop using a thing. Usually this comes down to selecting tools based on open technology.
Basically you can implement websocket like functionality, without using websockets. Super simple and robust realtime messaging from your php server code to your JS frontend, without dependencies.
Search for: text/event-stream
Glad to see that what was a horrible hack back then is now at least a proper standard. Thanks!