Controversial Adobe clones prove desktop Googlebook apps are closer than I thought

If you have spent any time following tech news or developer forums over the past couple of weeks, you have likely run into the massive controversy surrounding ArtCraft. Created by developer Brandon Thomas, the project set out to create a clean-room, open-source reimplementation of virtually all of Adobe Creative Cloud and Microsoft Office: spanning 13 separate desktop applications built in pure Rust.

To be completely clear upfront, I cannot condone ArtCraft on a legal or moral level. While Thomas claims the software was built using “clean-room” methods without Adobe’s proprietary code, the fact that Anthropic’s Claude AI co-authored over 60% of the codebase to visually mimic established commercial suites enters murky intellectual property territory. As photography veteran Aaron Nace pointed out in PHLEARN Magazine, the broader creative industry has serious ethical questions about where this trend leads.

However, if you set the controversy aside for a moment, a fascinating development just hit GitHub: a developer named MostafaXS1 has successfully created the artcraft-android builder. With pre-built ARM64 APKs now available for all 13 applications – including PhotoCraft, LightCraft, and VectorCraft – we are seeing fully functional desktop UIs running natively on Android. For Googlebook OS, that carries some pretty massive implications.

Real desktop UX compiled into native Android packages

One of the biggest worries currently hanging over Googlebook OS is the fear that users will be stuck in a blown-up phone app wasteland for the foreseeable future. Even with Google encouraging adaptive layouts, the general perception has been that porting complex desktop productivity suites to Android will be a long, drawn out challenge.

Seeing how these ArtCraft Android builds operate blows up that theory and after a quick download and install, we’re seeing:

• Native Rust, not a web wrapper: These aren’t sluggish web shells. They are pure Rust desktop apps compiled directly into native 64-bit ARM Android packages (NativeActivity).
• Desktop-First Workspaces: Instead of oversized touch targets, the UI provides dense interfaces, multi-track timelines, floating panels, and full keyboard-and-mouse navigation out of the box.
• True File System Integration: The Android builder hooks directly into Android’s Storage Access Framework (SAF), registers system fonts, and even wires up desktop file associations (like automatically opening .psd files directly into PhotoCraft).

Rough around the edges, but the roadmap is clear

Make no mistake: these fledgling applications are not ready to replace your daily production workflow. According to the project’s own progress trackers, PhotoCraft is only about 45% ready for real work, while LightCraft sits at roughly 61%. Menus can be clunky, advanced generative tools are missing, and camera RAW profiles are still basically estimated.

Yet despite those rough edges, the tactile experience of opening them on a laptop canvas is undeniably desktop-class. The windows, toolbars, and keyboard shortcuts behave exactly how power users expect when they open a $1,000 laptop.

If a solo developer and an open-source contributor can leverage AI tools and Rust to compile 13 dense, desktop-grade creative and office applications into native Android APKs in a matter of weeks, larger software houses don’t really have any excuse at this point. The Android 17 underlying architecture is fully capable of driving serious desktop software right now. ArtCraft may be wrapped up in controversy, but the implications of what they’ve delivered gives developers a clear roadmap for the future of Googlebook OS software.