Feedback wanted - pusha.io
I am currently trying to grow the subscribers of www.pusha.io and would like to hear your feedback. Pusha is a push notification service for developers who do not wanna build their own app just to send notifications.
- When you visit the website, is there anything which is not clear or could be improved?
- Do you have an idea where I could find more developers who are in need of instant notifications?
- Would you use a product like this and would you pay $1.99 per month?
Damnit! We are actually working on a similar product right now.. well, looks like we have to release earlier than expected.
Anyway, you can expect some healthy competition in the near future ;)
Looking forward to see your product :)
Why only for mobile users? why not for websites?
I see a need to push notifications to my users ex:- Inform them about offers, discounts, Survey requests, etc.
I don't want to update my site for notifications. I just want something like pusha.io javascript(just like crisp.chat) into my site and I should be able to notify users(like a popup on the top with a timeout). As a advanced feature I should be able to recognize if the user is a first time user and then show a different notification, location based notification etc.
Definitely something I will think about.
It looks like a good product, but it doesn't have anything that could pull me away from Pushover.
We offer social authentication, support of multiple recipients (which only works with groups in Pushover) and no message sending limit of 7500 per month.
Cool, is all of that information on your website? If you've got perks that are beating the competition, flaunt them!
Please excuse my ignorance (although hopefully good feedback). I'm not sure how this is any different to Pushover and in fact has a few less uses than Pushover does.
We use Pushover as a daily tool in our office. People have the client loaded as a pinned tab in their browser (or using the unofficial Linux client). We use it for personal notifications, such as a ticket being assigned to someone, a system down or one of their scripts needing assistance. The support phone (used by the person on call) is also contacted via Pushover when there is an issue.
The key things from my point of view...
I hope that helps
Thanks for the honest feedback. This is exactly the use case what I imagine for those push notifications. I will add a Curl example to the documentation, good point. Regarding the uptime, we already have a solid system with load balancer, auto scaling and an upcoming SMS notification service (as failover) which should bring us close to 100%. We opted for a monthly fee to secure a healthy money flow for the future and ongoing development work.
Couple things that stand out for me:
Skip the first step of creating an account on the web and immediately prompt to download the app; people can sign up through the app itself.
Why have a mobile app in the first place? When I integrate this type of thing it's on my laptop as it ties in with my workflow - my laptop is where I build stuff so needing my phone feels awkward.
True, removing the (web) account creation could help with on-boarding. Before I do that, I def have to improve the app as the current registration (within the app) only opens the browser.
"Send push notifications from your web or desktop application to your smartphone"
'your' sounds like it's only for developers to send notifications to themselves. And I don't quite understand transmitting from 'application' to phone - can you send from web/desktop client to phone, or does it get authorization or route through your server?
I think the API page needs to talk about authentication/authorization and what a 'user' is defined as.
Also the iOS/Android app - Is there any code you need/can write to receive notifications on the phone? Is it expected that your users install pusha? Can one pusha phone app be used with multiple pusha servers?
Thanks for the feedback. I really have to work on the message as other users pointed out as-well. Good point about the API, I will make it more clear what a user in this context is.
Hi, I love the design of the website and the service, just a couple of suggestions from my point of view:
Anyway good job 🤝
Great ideas. I already have some educational institutions on board and making it free for them could bring even more. :) Will try to emphasise the fact that you can keep track of your web/desktop app. Thanks!
You've done a nice job. I would suggest showing how easy it is to incorporate into an existing project. Your API page does this well.
The cost seems very reasonable, too. If I needed instant notifications like this, I'd sign up. For my needs, getting notified by email is sufficient.
Thanks. Yes, maybe I should show some sample integration on landing page.