Landing page and product docs for a serverless message queue SaaS - feedback welcome
This is my first foray into SaaS - and I keep getting told that early feedback is the way to go.
I published the landing page and product documentations for a serverless message queue SaaS that I am working on - pushmq.com.
The service works over HTTP. You push messages to PushMQ with a few configuration details along with where to send your message. PushMQ sends the message where you want it - when you want it.
Pushing a message is as simple as sending an HTTP request to:
https://task.pushmq.com/example.com/a/long/path?_pmq_auth=<a_secret_access_token>&your_params...
For this, PushMQ will immediately send a request to https://example.com/a/long/path&your_params...
The product documentation outlines features that I, as a developer, would like to see in a SaaS offering of this kind.
The product targets serverless applications where maintaining the infrastructure behind a message queue is either counter intuitive or in some cases, impossible.
Bonus: This helps in bringing async design in all those shared hosting applications as well.
In my early days, as a young freelance web/php developer, I constantly felt the itch that I couldn't do heavy lifting in my applications without compromising UX. If I needed to, I would have to deploy infrastructure behind it, which was almost always impossible to maintain with the little budget we would get.
Want to resize an image - make the user wait!
Even today, message queues haven't evolved much in the face of serverless infrastructure. If I have to poll a service to get new messages, I don't believe it's truly serverless!
PushMQ is my answer to that!
Note: the
task.pushmq.comsubdomain is not active yet
Nice idea, queues is definitely something that's currently missing with a lot of popular hosting services.
A few ideas to improve your design.
@Eelco thank you for the detailed review.
All these are good points - let me look into them.
I haven't really given thought to giving code examples on the landing page. Sounds promising. It will probably help visitors in understanding and will also act as a nice segway to the docs (where the code examples actually are)
A live example is going to be a little more difficult, since I haven't actually put this up in a publicly accessible server yet! Warrants a bit of thought.
A shout-out to @markosaric for the incredible plausible.io service. Integration was a breeze - and instant data. Thank you for your work.
Feedback from a design angle made after looking at it for 1 second: My eye is not sure where to go. The "Message Queue for serverless", the primary button and the screenshot on the left are battling for attention. I would strive for a clear 1-2-3 hierarchy here, depending on what you consider most important.
Thank you for the design angle. Really need input on that.
UI has never been my strong suite.
I will have another go at it.
Thanks
@blackbrokkoli I updated the landing page and removed the screenshot along with updating the font size of the header.
Nice! IMO definitely better from a design angle.
Without any images it looks very tech-y (like I am on the start page of software docs, as opposed to the sleek look a marketing startup or whatever might have), but honestly that might be just right for your audience (which I would presume is highly technical).
I think your next step is to get someone's eyes on it who is in your target group - never used serverless so not me sadly ;)