Nextjs pages router doesn't work about nextjs-tailwind-ionic-capacitor-starter HOT 1 CLOSED

Hi @SunPj, you have two options when building a mobile app with Next.js: static export or classic remote-loaded.

Static export means you have to sacrifice any features that require a server because you have no server environment when running locally in the native app environment. While this seems extremely limiting it's really not, you will just build more of a classic SPA and use client-side routing (such as Ionic's router if you are using Ionic, or another framework's routing solution, or roll your own).

The other option loads your Next.js app remotely. You can use all Next.js features because it's just like any other Next.js deployment. This sounds great, right? Well there are significant trade-offs to think about with this approach. The first is that your app might not pass app store review if it doesn't feel like an app but rather just a wrapper around a website. This has nothing to do with it being web-based but Apple does not want apps that just wrap remote websites and add no other native features. The way to do this right is to have a mix of offline/local experience and the remote app to make the app feel great and fast on launch and not be obviously just loading a remote website. This can be partly done by configuring the server.url config value in Capacitor: https://capacitorjs.com/docs/config

from nextjs-tailwind-ionic-capacitor-starter.