After spending way too much time testing push notifications across different mobile projects, I finally built a tool to solve my own workflow—and today it was approved on the Mac App Store. 🎉

As a mobile developer, I constantly need to test push notifications for React Native, Flutter, and native iOS/Android apps. Every time I wanted to send a test notification, I'd end up writing a small backend, running scripts, or waiting for a staging environment just to verify a payload.

It got frustrating enough that I decided to build a macOS app instead.

Push Tools lets me send and debug push notifications directly from my Mac without any backend. It currently supports:

• Expo Push Notifications
• Firebase Cloud Messaging (FCM)
• Apple Push Notification service (APNs)
• Live Activities (ActivityKit)

The workflow is simple: choose the provider, paste a device token, write your payload, and send. You immediately get the response back (status, errors, ticket ID, etc.), making it much faster to debug notification issues.

One thing that was important to me was privacy. There are no accounts, no subscriptions, no telemetry, and no cloud servers. Everything runs locally, credentials are stored in the macOS Keychain, and requests go directly to Apple, Google, or Expo.

I also added a Device Book for saving tokens and JSON import/export so I can quickly replay notification scenarios during development.

This started as a side project purely because I wanted a better workflow for myself, but I figured other mobile developers might find it useful too.

I'd genuinely love feedback from other developers:

• What does your push notification testing workflow look like today?
• Is there anything you'd want a tool like this to support?

Mac App Store: https://apps.apple.com/us/app/push-tools/id6771867496?mt=12

Hi everyone

Over the past few weeks I've been learning Rust and Tauri, and instead of following tutorials I decided to build something I'd actually use.

The result is WaLinux—a lightweight native wrapper around WhatsApp Web designed specifically for Linux.

GitHub: https://github.com/theany-org/WaLinux

Why I built it

I wanted a simple WhatsApp desktop client for Linux that felt more native while also giving me a real project to learn Rust and Tauri.

I'm still a student and definitely not a Rust expert, so this project has been a huge learning experience.

Current features

• Native Linux notifications
• Session persistence
• Window state memory
• Better download handling
• Scoped Content Security Policy (CSP)
• Lightweight with low resource usage

Why I'm sharing it

There are still lots of things that could be improved, and I'd love to make this a community project.

If you're interested in Rust, Tauri, Linux desktop apps, or just want to contribute to an open-source project, I'd really appreciate your feedback or pull requests. Even small contributions like bug fixes, documentation improvements, or feature suggestions would help a lot.

I'm especially interested in hearing:

• What features would make you switch to a native WhatsApp client?
• Any code review or Rust/Tauri best practices.
• Ideas for improving the Linux experience.

Thanks for taking a look! I hope someone else finds it useful too.