Live betaNativeOffice
Your documents. Your machine. An office suite that stays with you.
A native desktop office suite with Writer, Sheets, and Slides. Built in C++ and Qt6, it works without an internet connection, ships under 100 MB, and collects no telemetry.
I built the product and the infrastructure around it: authentication, packaging, updates, referrals, and the path from download to a working desktop application. NativeOffice is in beta on the Microsoft Store, with mobile versions in progress.
I am the founder and CEO of NativeOffice. Within two months of launching the website, it gained over 100,000 views. The product is now approaching 1,000 registered accounts.
What if your office suite belonged on your machine?
NativeOffice brings documents, spreadsheets, and presentations into a native desktop product, then extends the workspace to the browser.
Writer · Sheets · Slides
Three familiar kinds of work in one native C++ and Qt6 desktop suite.
Offline by design
The desktop workflow keeps files local and remains usable without an internet connection.
A connected workspace
A browser companion adds collaborative documents, spreadsheets, presentations, and design tools.
Start with the work people do every day.
NativeOffice is built around the everyday cycle of writing, calculating, and presenting. Writer handles documents; Sheets gives structured information a working surface; Slides turns material into a presentation. The native desktop suite is the foundation, with Windows distribution through the Microsoft Store.
Its central architectural decision is C++ with Qt6. An offline desktop workflow puts the application and files on the user’s machine, making a lost connection less disruptive to the core work. The engineering includes packaging and delivery as well as the editor interfaces themselves.
Local work. Shared work. One product direction.
The product now also has a browser workspace with Docs, Sheets, Slides, and Design. Its public site describes real-time collaboration, shared editing, templates, and account access across the product. The browser experience broadens the ways someone can begin a document or work with other people.
There are also bridges toward technical workflows: the product advertises converting spreadsheet selections into pandas-oriented Python and exporting selected material as Markdown. Those features connect office work with analysis and developer tools. macOS, Linux, and mobile editions remain roadmap items on the product site; the published desktop release is for Windows.
Build everything between an idea and a user.
As founder and CEO, I work across the product, engineering, and distribution. That includes the desktop application, authentication, release packaging, updates, referrals, and the website that brings people to the download. Cloudflare Workers, D1, OAuth, and MSIX support the machinery around the native suite.
Within two months of launching, the website gained 100,000+ views—over one lakh—and NativeOffice is approaching 1,000 registered accounts. Those figures describe different stages of adoption: website views reflect reach, while registered accounts record the people who have signed up. The next product question is how that initial interest becomes an everyday habit.
How it comes together.
Discover
A public product site explains the suite and directs people to a release or the browser workspace.
Create
Write a document, work through a sheet, or build a presentation in the appropriate tool.
Work your way
Use the native desktop offline or choose the browser workspace for connected collaboration.
Keep shipping
Packaging, account infrastructure, and updates turn an application into an ongoing product.
A closer look.
Explore the interface, the work, and the details behind it.
A product is bigger than its editor.
NativeOffice demonstrates the full path from native application engineering to distribution and adoption. Its next challenge is turning early reach into sustained everyday usefulness.