JHipster in a Mobile World

In June 2019 I spoke at JHipster Conf 2 in Paris on taking a JHipster backend all the way to a published mobile app. The full recording is below.

JHipster in a Mobile World: From Generation to the App Store — JHipster Conf 2, Paris.

What the talk covers

JHipster is best known for generating a Spring Boot backend with an Angular, React, or Vue web client. But that same backend can power a mobile app, and JHipster gives you a few ways to get there. The talk walks through the options and the trade-offs between them:

• Progressive Web Apps — the lowest-effort path. Turn on PWA support and your existing web client becomes installable and offline-capable. There's no second codebase to maintain, but you're still living inside the browser.
• Ionic — wraps an Angular UI in a native shell through the official Ionic module for JHipster. A comfortable fit if you're already an Angular shop, and you get access to native device APIs.
• React Native — a fully native UI rendered from JavaScript, generated with ignite-jhipster. This is the path I focus on, because it gives you real native components instead of a web view.

For each option I compare what you get against JHipster's Angular and React web clients — what carries straight over (authentication, the entity model, the API wiring) and where a mobile app needs its own thinking, like navigation, offline state, and the requirements of the app stores.

The demo

The heart of the talk is a live, end-to-end demo:

1. Start from an existing JHipster backend and its entities.
2. Generate a React Native client against that backend with ignite-jhipster, wiring up authentication and the API for free.
3. Generate several entities so the app has real screens to work with, then run it on a simulator.
4. Build the app and walk through what it takes to get it onto the App Store.

The point is to show that the distance from "I have a JHipster API" to "my app is in the store" is a lot shorter than people expect. The generator handles the boilerplate, so your time goes into the parts that are actually specific to your app.

Takeaways

• If you already have a JHipster backend, you're most of the way to a mobile app. Pick the path — PWA, Ionic, or React Native — that matches your team and how native you need the result to feel.
• React Native via ignite-jhipster gets you a genuinely native UI while reusing your backend's auth and entity model.
• Generation gets you to a running app fast; the real work is the app-specific layer, which is exactly where you want your time going.

If you want to try the React Native path yourself, my Ignite JHipster walkthrough covers the setup step by step.