2020-01-31
1387
#js libraries
Anjolaoluwa Adebayo-Oyetoro
13342
Jan 31, 2020 ⋅ 4 min read

Introduction to Inertia.js

Anjolaoluwa Adebayo-Oyetoro Maker. Writes sometimes. Playful most times. Loves beautiful UIs.

Recent posts:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 ⋅ 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 ⋅ 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 ⋅ 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 ⋅ 12 min read
View all posts

4 Replies to "Introduction to Inertia.js"

  1. Hi, thanks for your analysis! When you write : “Of course, there are times when using Inertia might not be the best fit. Situations such as when you need multi-client support”, what type of multi-client support scenario are you referring to? Thank you

  2. I believe he is talking about building an app that may require multiple clients, i.e. you need both a web app and a mobile app. Then it may be better to build a stand-alone api that you use in both clients.

  3. In my opinion, that shouldn’t be a limitation since Laravel support API routes. One can have a monolith web application and still support other application types.

Leave a Reply