rogerluan
Joined 10 years ago
Joined 10 years ago
Using the words of one of the customers I have: "it shifts the paradigm from us needing to pull information to getting it pushed to us! Really helpful!"
It frees up time of mobile developers' and democratizes the access to the information across different departments :)
Lemme know if there are other questions I can help answering! Happy to explain anything in further details
Key features:
- Real-time Slack notifications for iOS and Android app review statuses. - Instant alerts for TestFlight releases for your internal team and external testers. - Updates on app processing changes, all in one place. - there's more, but those are the main features
Happy to answer any other questions you might have! I wonder if the landing page isn't clear enough; is there anything you'd improve on it?
You'll notice that the subscription is based on workflows. A workflow is a connection between a source (e.g., your iOS app) and a destination (e.g., a Slack channel). You can set up as many workflows as you'd like, which is a great way to separate different types of notifications. For instance, #ios-deploys-prod receives updates about your production app, #ios-deploys-staging receives updates about your staging builds, and #android-deploys-beta receives updates about the Beta track of your Android builds. Each of these is a separate workflow.
Now you can find all this in the FAQ: https://statused.com/faq#what-are-workflows
Great spotting, thanks once again!
I'll fix that right away.
PS: Lemme know if you need any guidance setting things up or have any further questions! There's the official support email but also white-glove treatment at t.me/rogerluan ;)
Although the future of Statused holds more than just forwarding emails to Slack. I intend to add support to other "channels", such as Teams, Discord and Telegram, as well as other types of integrations such as incoming webhooks, so a status update could directly trigger a custom action in your CI/CD pipeline, for example "detect the app has finished processing, then submit it for review".
On top of that, I don't think you get those emails for every Google Play changes that are made to your release, so not sure if that would work. Again, this might work, but I'm really not sure.
You have a point with those concerns about sharing API keys. But this has become pretty standard and devs share those keys with a bunch of services already, such as as with CI systems, app store user review services, sometimes ASO monitoring tools even.
The FAQ page highlights which permissions the API keys need: https://statused.com/faq#which-permissions-does-my-google-pl...
Thanks for raising these points! It's valuable feedback to understand how people perceive this product!
The cool thing is that I don't intend to take it down now that I built a SaaS around it. I'll keep both open source and SaaS versions of it live, and try to upsell the service to those who don't feel like self-hosting it. Plus, the SaaS version comes with features not available in the open source version (such as support to Android) :)
Thanks for spotting and sharing this!
I agree with your points. The point of gathering the API key is to actually be able to provide a lot more information in the future, such as some light data science (analytics) into your releases, and maybe expand to other areas (e.g. taking actions from the Slack messages themselves).
What do you mean with "like a real mail-filter"?
The RSS feature is kinda on the roadmap but I haven't gotten any feedback about users wanting that type of integration. Incoming webhooks is higher up in the list, so users can trigger internal CI actions upon receiving requests to such webhooks.
Any other type of APIs you'd like to see this tool covering? :)
I also like the gamification aspect, is there anywhere I can check what are all the badges/achievements I can get (so I know what to target)? If not, any plans to make that visible?