nextjs-tailwind-ionic-capacitor-starter VS transferred-stepzen-schemas

wow, that's a weird limitation.

The README says: "SSR is currently disabled for the Next.js app as the app will be fully client-side rendered for iOS and Android. This is a limitation we are working to address in a future update."

I guess it's because CapacitorJS pre-bundles the entire PWA for the App Stores:

"Of course, you also could load the app completely remotely by changing the server.url configuration for Capacitor to point to your SSR'ed Next.js app, but that has other challenges such as App Store approval if the app doesn't check the boxes for Apple to qualify it as an app that has enough native integration (at that point this is on you, not Capacitor)"

https://github.com/mlynch/nextjs-tailwind-ionic-capacitor-st...

But I don't understand why SSR would be disabled for the NextJS PWA on the web?

Maybe Max Lynch aka. @mlynch aka. @yesimahuman could provide some insight here.

If you want to use something like tailwind to customize the content of your pages, that is a decent option. You would use Ionic for the shell and Tailwind for your page designs. Take a look at this example if you want to explore that route (in React though): https://github.com/mlynch/nextjs-tailwind-ionic-capacitor-starter

Max Lynch from Ionic has a great repo demonstrating this. He uses it to get Next to work with Ionic and Capacitor but the idea is essentially the same.

Agreed! Next.js works great with this model! I’d recommend Capacitor over Cordova (similar but more modern). Here’s an example: https://github.com/mlynch/nextjs-tailwind-ionic-capacitor-st...

You can use Next with React Router, making it function exactly as a React app with nested routes. This project shows this working with Ionic's router, but the same setup can be used with React Router for the same outcome.

Also, note that this repository is a boilerplate for all 3, which uses ionic capacitor, in one repository: https://github.com/mlynch/nextjs-tailwind-ionic-capacitor-starter , I guess it is not using nextjs SSR capability though.

If you're confused by all the project names and how they work together, don't worry, I'll break down each part of the stack each project is concerned with, along with some visuals and code samples demonstrating how all the projects work together. At the end I'll share a starter project with these technologies installed and working together that can form the foundation of your next app.

Go to stepzen.com and click on the start for free button.

Either way, I'm not too familiar with RxDB but looking at the docs you can also use StepZen to create the GraphQL layer that you use for replication. With StepZen you can build and deploy a GraphQL API based on multiple datasources (including MSSQL) in minutes. That way you only have to worry about building the logic that pulls and push replicates data to and from GraphQL. How you structure the MSSQL database would become the most important part of this project, to ensure a smooth replication.

There are multiple ways to get a GraphQL API on top off a Postgres database. If you want to have a GraphQL abstraction layer that runs as a hosted service and needs almost no code, have a look at StepZen. You can build a GraphQL API for the Postgres database by following the docs here. StepZen introspects the database (using stepzen import postgresql) and let it create the schema for you based on all the tables and columns of your database. Including a set of queries to get started with.

If you’re looking for a managed service, have a look atStepZen. You can combine multiple GraphQL schemas into one cloud GraphQL API. Instead of writing a gateway yourself, you can use SDL to merge different schemas. Besides GraphQL APIs you can also “federate” other data sources like SQL or REST

There are many of them, including StepZen which is language/framework agnostic and let you create a GraphQL server with GraphQL SDL only - in a declarative way

I’ve seen more products letting you join/merge GraphQL schemas independent of schema stitching or federation. Have a look at GraphQL Mesh or StepZen.

You can save yourself the hassle of having to build a GraphQL server, resolvers and database connections with StepZen (https://stepzen.com). It’s a product that is based solely on GraphQL SDL and you set the database connections with directives. Also, you can use it to connect other APIs

There is one thing I can say for sure: I love the spirit of open source. I've had a wonderful time working with open source communities of different sizes (e.g. Seneca-CDOT, StepZen, Appwrite, and Zulip). Fortunately, all of them are fantastic and patient with beginners.

If the only thing you're trying to do is converting a REST API to GraphQL, you should have a look at https://stepzen.com/

StepZen filed an issue about writing a GraphQL schema to integrate SpaceX REST API into their React application. I found this as an excellent opportunity for me to learn GraphQL.