NativePress case study

My role

I designed and built the plugin, the app and the data format between them. I also handle the preparation of an app for store submission for clients. Apple and Google decide approval.

The problem

A WordPress site is often the best source of content a business has. Many "WordPress to app" products wrap the website in a WebView. That gives a browser inside a shell. The default WordPress REST output is also heavy for a phone, because it sends a lot of HTML and fields the app never uses.

Site owners want their authors to keep writing in the editor they know, and they want the app to feel like an app.

The approach

The plugin adds its own REST namespace, nativepress/v1. It takes what authors write in Gutenberg, turns the HTML into light Markdown and serves that. It does not use the default wp/v2 output.

The app is built with Expo and React Native. It reads the Markdown and draws it with native components. Authors do not change how they work. WordPress stays the source of truth, and the client keeps the site, the hosting and the domain.

I sell it as a subscription: a monthly plan plus a one-time setup fee. Ask for a quote.

Stack

React Native, Expo, a WordPress plugin, a REST namespace nativepress/v1 and Markdown, as listed on the demo page.

Screens

Mock-up and illustration with sample content

These are not screenshots of a live customer app. One is a mock-up and one is an illustration.

What is public and what is not

Public: the idea, the REST namespace name, the stack, the pricing model in words and the two images above. The product site is nativepress.app.

Not public: customer sites, customer apps, store listings and any numbers about downloads or sales. I do not claim any. I do not guarantee store approval, downloads or rankings.

Related pages

• NativePress on the demo page
• Mobile app development service
• WordPress development service
• All selected work