Previously, setting up your first workflow involved 4 steps:

1. Add an API key (App Store Connect or Google Play)

2. Add your app manually

3. Add a destination (e.g., Slack, custom webhook)

4. Create your workflow and connect everything

The second step—adding your app—was often a pain point, so we removed it 🎉

Now, when creating a workflow, you’ll see a dropdown of all your apps (for App Store Connect). No need to register them manually anymore.

For Google Play, you’ll still enter your package name, but the flow is much more streamlined.

We also:

• 🛠 Fixed a few edge cases where webhook destinations failed to deliver notifications

• ☑️ Added validation when saving API keys, so you’ll immediately know if they’re valid and have the right permissions

• 🔐 Patched a minor security issue related to Google Play integration

As always, we’d love your feedback. Let us know what you think and feel free to request new features!

We recently fixed a bug that prevented new customers from starting their subscription from the billing page. This issue was introduced about two weeks ago and is now resolved.

If you joined during that time and couldn’t start your subscription, everything should work smoothly now.

Let us know if you run into any issues — we’re here to help!

We listened to your feedback!

You can now send test notifications directly from your workflows — a small quality-of-life improvement to help you verify setup and debug issues with app fetching or delivery.

You can find this new button under "actions" in your list of workflows.

Enjoy! 🎉

Statused was originally built quickly — as most MVPs are — but it started to show its limits:

• Adding features felt like duct-taping spaghetti code.

• It wasn’t optimized for speed or reliability.

• LOTS of duplicated code everywhere, due to lack the of reusable components

• The open-source roots made onboarding new users clunky.

So I rebuilt it with a clean architecture, powered by Next.js. This brings:

• ⚡️ Faster performance and better DX

• 🤖 Easier integration, by adding nice touches of UX

• 🧩 A solid foundation for upcoming features

To some specific improvements:

• If your app identifier is the same between Android and iOS, now it's clear which one you're managing

• Adding API keys is easier by allowing you to drag and drop your auth files

• Now you see a nice preview of what your workflow will do once created. No more guessing!

• Dark mode 🌙

• A bunch of minor bug fixes!

There's still so much to be improved, but we feel this is a solid start! We're looking forward to continuing the improvements over time, so stay tuned!

And if you have any feedback, feel free to reach out! 👋

In this release, we’re excited to share a few quality-of-life improvements:

• 🔨 You can now test a destination by simply pressing a button next to it. This sends a sample notification to your destination, helping you confirm it’s working correctly.

• 🔗 Based on customer feedback, we’ve added helpful links to the top of your dashboard. These include a quick link to our FAQs and a link to check the system status.

• 🐛 We’ve resolved some minor issues to improve your overall experience.

P.S. We’ve also added a footer link on the landing page that leads to these logs 😉 If you came here through that link, hello 👋

That’s all for now! Keep the feedback coming, they're super valuable! We’re here to prioritize your needs 😊

We’re thrilled to announce a long-awaited feature requested by our customers: outgoing webhooks! 🎉

While sending notifications to Slack is an excellent way to keep your team in the loop and democratize access to your app release updates, it’s primarily designed for human consumption.

With outgoing webhooks, you can now orchestrate powerful automations triggered by the same events you already know and love in Statused.

This new feature opens up endless possibilities to integrate Statused into your workflows, enabling seamless automation beyond Slack.

You can visit this FAQ to learn more about the webhook payload format and capabilities.

We'd love to hear what workflows you're creating using Statused! Hit us up any time at x.com/StatusedApp or hi@statused.com

Hey, everyone! 🌟

Welcome to the very first post documenting the updates we’re making to Statused! 🚀 From now on, this page will serve as a log for all the changes — big and small — that we ship to you.

If you’re new here, here’s a quick rundown of what Statused can do for you:

• Monitor app review statuses for your Android and iOS apps in both Google Play Store and the App Store.

• Notify your team on Slack about key updates:

  • When your app’s review status changes (e.g., “In Review,” “Rejected,” “Ready for Sale”).

  • When TestFlight builds become available for testing.

  • When “Pending Agreements” in App Store Connect require attention before further updates can be made.

• Send updates to as many Slack channels as you want through multiple workflows, enhancing team organization.

• Integrate seamlessly with Slack, supporting both Incoming Webhooks and Slack Workflows.

• Allow you to keep a permanent and searchable history of all app releases, rejections, and TestFlight statuses within your Slack channels.

• Empower all team members — including QA, marketing, project managers, and engineers — to stay informed about app statuses without creating a dependency on your development team to let the rest of the team know of those updates.

Stay tuned for more exciting updates coming soon! 🚀

Cheers,
Roger
Creator of Statused