- Preface
- 1 Introduction
- 1.1 The app you will build
- 1.2 The idea behind Ionic
- 1.3 The way through this book
- 1.4 What to install
- 1.5 The code for this book
- 2 Angular Essentials
- 2.1 What is Angular?
- 2.2 Standalone Components
- 2.3 Signals
- 2.4 Dependency Injection with inject()
- 2.5 Lifecycle Hooks
- 2.6 Data Binding
- 2.7 Pipes
- 2.8 Built-in control flow
- 2.9 Routing and Loading
- 2.10 Observables
- 2.11 Promises and async/await
- 2.12 Signals, Observables and Promises — which one when
- Summary
- 3 The first app
- 3.1 Creating an app
- 3.2 Running it
- 3.3 The first change, without a reload
- 3.4 What the CLI generated
- 3.5 What a fresh Ionic app is really like
- 3.6 BoB Tours — the app for this book
- Summary
- 4 Navigation
- 4.1 Have a plan
- 4.2 Generate the pages
- 4.3 Routes, and the outlet they land in
- 4.4 The shell around the pages
- 4.5 Forward, back, and the stack
- 4.6 The page you left is still there
- Summary
- 5 Services & Data
- 5.1 A server to talk to
- 5.2 From a signal to a request
- 5.3 Loading, error, data
- 5.4 The wire is not your model
- 5.5 Where data sleeps
- Summary
- 6 UI Components
- 6.1 Introduction
- 6.2 Accordion
- 6.3 Action Sheet
- 6.4 Alert
- 6.5 Badge
- 6.6 Breadcrumbs
- 6.7 Buttons
- 6.8 Card
- 6.9 Checkbox
- 6.10 Chip
- 6.11 Date & Time Pickers
- 6.12 Floating Action Button
- 6.13 Grid
- 6.14 Icons
- 6.15 Inputs
- 6.16 List
- 6.17 Menu
- 6.18 Modal
- 6.19 Popover
- 6.20 Progress Indicators
- 6.21 Radio
- 6.22 Range
- 6.23 Refresher
- 6.24 Searchbar
- 6.25 Segment
- 6.26 Select
- 6.27 Toggle
- 6.28 Toolbar
- 6.29 Home
- Summary
- 7 Form validation
- 7.1 A form around the request
- 7.2 Fields get rules
- 7.3 A component that does not fit by itself
- 7.4 Fields that depend on each other
- 7.5 A half-written request must not vanish
- 7.6 Send
- 7.7 Success is a moment
- 7.8 The job is done
- 7.9 The right container for each control
- Summary
- 8 Theming, Styling, Customizing
- 8.1 The app in the shop window
- 8.2 One color, and what it changes
- 8.3 Two looks, one setting
- 8.4 Where a style lives
- 8.5 Ionic’s utility classes
- 8.6 A color of your own
- 8.7 Inside a component
- 8.8 Type
- 8.9 The logo
- 8.10 Motion
- 8.11 Dark, and who decides
- 8.12 The large screen
- Summary
- 9 Accessibility
- 9.1 Where the framework stops
- 9.2 Seeing what a screen reader sees
- 9.3 Structure: headings and landmarks
- 9.4 Keyboard and pointer
- 9.5 Text size and zoom
- 9.6 Contrast, and who asks for it
- 9.7 Motion, for those who asked for less
- 9.8 Messages that arrive on their own
- 9.9 Checking it stays that way
- Summary
- 10 Native functionality with Capacitor
- 10.1 The bridge that was there all along
- 10.2 An iOS project
- 10.3 Live reload on the device
- 10.4 An Android project
- 10.5 The safe area and the system bars
- 10.6 Remembering things
- 10.7 Share, and the FAB unfolds
- 10.8 Where the tour begins
- 10.9 Without a connection
- Summary
- 11 Debugging & Testing
- 11.1 Where to look first
- 11.2 The browser’s DevTools on BoB Tours
- 11.3 Angular DevTools
- 11.4 The app in its shell
- 11.5 The first test — asking the form
- 11.6 Ionic and Signal Forms together
- 11.7 The submit boundary
- 11.8 The HTTP boundary
- 11.9 Now break something
- 11.10 Checking it stays that way, automatically
- Summary
- 12 Build, Deploy & Publish
- 12.1 What is left to do
- 12.2 The build, now that the app is whole
- 12.3 Where the API lives
- 12.4 Which number the store reads
- 12.5 Icon and launch screen
- 12.6 What Apple wants declared
- 12.7 One app, two languages
- 12.8 A signed Android artifact
- 12.9 The iOS archive
- 12.10 The same app, as a PWA
- 12.11 A build pipeline with GitHub Actions
- 12.12 Live updates after Appflow
- Summary
- Bonus 1: Ionic with or without frameworks
- B1.1 What changes if you move
- B1.2 An app with no framework at all
- B1.3 Who pays for the work
- B1.4 What you can plan on
- B1.5 What your team brings along
- B1.6 Beyond the app
- B1.7 Two portraits
- B1.8 The decision, and when it goes the other way
- Summary
- Bonus 2: Ionic and AI
- B2.1 Two questions, kept apart
- B2.2 The key stays on the server
- B2.3 The form assistant
- B2.4 What it costs, and what the stores want to know
- B2.5 A rule, the phone, or the cloud
- B2.6 What an assistant builds, and what it needs to know
- B2.7 Two assistants, two roles
- B2.8 When nobody is watching
- B2.9 When it pays off
- No summary
Ionic 9
Create awesome and AI-able apps for any platform
This book is 100% completeLast updated on 2026-09-28
Build one real app, from the first ionic start to a signed release, with Ionic 9, Angular 22 and Capacitor 8. Every starter, build and test in this book was checked against the real toolchain, and the app's code along the way is waiting in a public repository.
Minimum price
$59.00
$69.00
You pay
Author earns
PDF
About
About the Book
This book does not teach Ionic as a box of unrelated components. It builds one application, BoB Tours, the app of a fictional tour company in Bonn, step by step, and lets each new concept solve a real problem when that problem appears.
What you build along the way
- A project from
ionic start, pages to move between, and live data from a server withhttpResource() - Ionic's UI components, each one moving the app forward, and arranged so the chapter doubles as a catalog
- Forms with Signal Forms, theming and dark mode, and layouts that use the space of phone, tablet and desktop
- Accessibility: headings and landmarks, keyboard, text size, contrast, and automated checks with axe
- Native features with Capacitor 8 on iOS and Android, including a life without a connection
- Debugging, tests with Vitest, and the way out: signing, the iOS archive, a PWA and a pipeline on GitHub Actions
Two bonus chapters follow. Ionic with or without frameworks helps you choose between Angular, React, Vue and none at all. Ionic and AI adds a form assistant to the app without handing its key to the phone, and then asks what a coding assistant builds for you, and when that actually pays off.
The modern stack. Standalone components, Signals, zoneless change detection, OnPush and Vitest, used where they earn their place. The examples are not based on remembered behavior: starters, builds, navigation, network requests and tests were checked against the real toolchain while the book was written.
What you need. HTML, CSS and JavaScript. Not Angular, TypeScript or experience building apps; those are what the book is for. The chapter on Angular is written to be returned to, so if you already know it, start with the first app.
The code. The app's state along the way lives in a public GitHub repository under the MIT license, so you can compare your code or join at any point.
This edition is an accessible PDF (PDF/UA-2): navigable headings, and a text alternative for every figure.
Earlier editions of this series were called "practically unrivaled" by c't and "one of the best Ionic books of all time" by BookAuthority, and they are used in university courses from Arizona to Brunei.
Feedback
Author
About the Author
Andreas Dormann
Andreas Dormann is a lecturer and head of the Center for IT and Media Didactics at the University of Applied Sciences for Law in North Rhine-Westphalia and co-founder of the Federal Association for Digital Teaching at the Universities of Public Services in Germany. With over 30 years of experience, Andreas has been instrumental in developing cutting-edge software, e-learning platforms, and innovative mobile apps.
Contents
Table of Contents
Get the free sample chapters
Click the buttons to get the free sample in PDF or EPUB, or read the sample online here
The Leanpub 60 Day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms...
Earn $8 on a $10 Purchase, and $16 on a $20 Purchase
We pay 80% royalties on purchases of $7.99 or more, and 80% royalties minus a 50 cent flat fee on purchases between $0.99 and $7.98. You earn $8 on a $10 sale, and $16 on a $20 sale. So, if we sell 5000 non-refunded copies of your book for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earned over $15 million writing, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
Learn more about Leanpub's ebook formats and where to read them
Write and Publish on Leanpub
You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses!
Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks.
Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. (Or, if you are producing your ebook your own way, you can even upload your own PDF and/or EPUB files and then publish with one click!) It really is that easy.