OpenClaw releases iOS and Android apps with secure pairing and push alerts

• steipete’s launch thread said OpenClaw’s new iOS and Android apps shipped with secure pairing and push notifications after a community build effort.
• In steipete’s follow-up, he said the team pushed an early release to attract contributors instead of letting "30 separate apps" fragment the work.
• steipete’s security reply said the project spent months on security work, coordinated with Nvidia, Atlassian, and Microsoft, and spun up a separate site to help other projects.
• Funding is still thin, according to steipete’s sponsorship reply, which said the project had received one donation while other support was still under discussion.

You can trace the launch back to steipete’s main post, then jump to his security reply for the enterprise angle and his App Review note for the less glamorous part, the apps reportedly sat in review limbo for months before they finally surfaced.

The headline is simple: OpenClaw now has mobile clients on both major platforms. In steipete’s main post, he said getting iOS and Android working required secure pairing, push notifications, and clearing both app review processes.

That post also drew a line around ownership. According to steipete’s main post, OpenClaw was not acquired by OpenAI and is not an OpenAI product, even though OpenAI covers token usage.

The team’s logic for shipping early was blunt. In steipete’s release-timing reply, he said maintainers wanted one shared app people could notice and join, rather than more parallel one-off clients.

The launch doubled as a recruitment post. In steipete’s contributor reply, steipete said the project lacked enough people, and his Discord note pointed would-be contributors to the #clawtributors channel.

Money looks even tighter than attention. steipete’s sponsorship clarification said Microsoft does not sponsor the project, while his funding reply said the team had only one donation so far.

Some of the slowdown was organizational, not technical. In steipete’s App Review note, he said many community members shipped their own versions instead of contributing upstream, and the mobile app then spent months in App Review limbo.

The most concrete post-launch claim was about hardening. In steipete’s security reply, steipete said the team had worked for months to secure OpenClaw, cooperated with Nvidia, Atlassian, and Microsoft, and built a separate security resource for other projects too.

The same thread surfaced the current support edges:

• steipete’s plugin bug reply said one reported problem came from Lossless, a third-party plugin, not OpenClaw itself.
• steipete’s Anthropic reply said Anthropic blocks competitors, which limits at least one integration path he was asked about.
• steipete’s token-sponsorship reply said OpenAI’s token support was what made the project exist at all.

That leaves OpenClaw in an interesting place: mobile is live, enterprise teams are apparently already shipping it per steipete’s security reply, and the maintainers are still staffing up the basics in public.