rogerluan

I signed up and I really like the custom domain feature, this is really valuable to me, personally :)

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?

Thanks! If you do go back to working with mobile apps in the future, don't forget to check it out :) even if the project doesn't get any customers, I don't intend to shut it down, because it's super useful to me personally, so it should be up and running for years to come ;) — assuming Google/Apple doesn't kill or sherlock it lol

Statused is crafted for app developers, project managers, and QA teams who crave efficiency and a central point of communication for their app's release cycle. The larger the team looking to streamline its process, the better.

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

It's for Android/iOS apps, thus, app approval/rejection from e.g. Apple, but also applies to other app statuses too :)

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?

So, "what are workflows?"

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!

Oh this tool is not for web apps though, just mobile apps distributed to Google Play Store and App Store :)

I checked Tramline and it sounds like a great tool! It definitely deserves more attention!

Ooh, that's super valuable feedback, thank you so much!

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 ;)

Thank you! I'm really excited for this!! Gonna continue building things that solve pain points I have in my daily routine, which might be useful to others too lol

That is definitely one way to solve this specific problem, you're right!

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!

Yup, that repo is mine! haha

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!

Thanks for the feedback!

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? :)

This is amazing!! Congrats on putting together all that functionality!

How many users are using that service? How come you decided to make it 100% free?

Your website is beautiful btw! I thought about building my tool as a Slack bot but thought that then it would be too limited to only Slack. I intend to add other types of workflows in the future, such as webhooks (to trigger special workflows in your CI) and a RSS feed :)

I'd love to connect with you if you wanna work together on something! t.me/rogerluan

So, I put together a hacked version of this 3+ years ago (Aug 2020) in a few days and was up and running. We used this at my previous company for 3 years, until I decided to transform it into a micro SaaS.

The SaaS took 270 hours so far (so if I had done this in a typical 9-5 schedule, that would've taken me ~6-7 weeks). Sounds like too long, and it is, but considering I knew nothing about BE, FE, db, infrastructure, etc., and that I built it from scratch, completely ditching the previous version I had, it was quite a fun journey!

AMA :) happy to answer any other question

That's great feedback! You mean change the headline here on Hacker News, or the overall messaging shown on the landing page?

What would you suggest instead? I thought "No more 'Is the app live yet?'" would be clear enough, but I guess not

Yes, thank you!

I plan to add phased rollout user distribution too, so your team gets an update when the app rolls out to e.g. 5% of your users → 15% → 50%, etc…

Statused notifies your team of app and build status updates directly on Slack. No more checking the App Store Connect website or waiting for emails!