In my mental model of an offline app, I expect instant responses. However, I know to the complexities of apps, the diverse wants of a big, diverse user base that it can be hard&#x2F;impossible for an app to be well-architected enough to achieve this ideal.Failover is hard, and there generally aren&#x27;t hard rules for what to do if data isn&#x27;t available or how to communicate to a user in a specific offline situation on how the current state of an offline app affects what they see -- and even when they would care or what they could do about it when they do care

&gt; Users expect near-native responsiveness, even when offlineDo they? I think users are amazed if anything works without internet with modern applications.

Seems a lot like FSharp Type Providers? Is that a good analogy?

I&#x27;ve got a similar project that includes a React component for the search input. The React component is actually a Monaco text editor so you get syntax highlighting, error highlighting, tab completion and more.Check it out here: <a href="https:&#x2F;&#x2F;github.com&#x2F;williamcotton&#x2F;search-input-query">https:&#x2F;&#x2F;github.com&#x2F;williamcotton&#x2F;search-input-query</a>There&#x27;s an animated GIF of the demo so you can get a very quick idea of how it works!

Nice, Ive bounced around between Prisma and Kysely too. I get nervous about locking too much into one thing, you ever worry if leaning on too much codegen or magic ends up biting you down the road?

any underlying negative consequences on letting prisma schema handle the underlynig model&#x2F;migrationsI found out about stackzen yesterday, really like the RBAC&#x2F;ABAC backed up into the models&#x2F;codegen stuff, been thinking about just using that for our custom logic and maybe add RLS pg a la supabase but also codegen from the same .zmodel from zenstack model that generates prisma models&#x2F;migrations have it generate RLS sql migrations codethoughts??also maybe postgres views to handle field&#x2F;attribute level security since rows is mostly about whole columnsmain goal is to secure the data at all the levels of the stack from db to api to app so there&#x27;s no footguns in the future where someone with a pg user or modifying our clients can see data they shouldn&#x27;t etc

I am using both prisma and kysely in the same codebase with a great success. The db schema is driven by SQL, not prisma. It is then introspected by both kysely and prisma, prisma is used in 95% of the places while kysely is used whenever performance is critical or when prisma doesn&#x27;t support the SQL features we need.

Looks good.For a more database specific, type-safe, data querying solution, I like to use <a href="https:&#x2F;&#x2F;kysely.dev" rel="nofollow">https:&#x2F;&#x2F;kysely.dev</a>

The same should apply to configuration, we have prisma for sql, we should have something like this for JSONs, like <a href="https:&#x2F;&#x2F;typeconf.dev" rel="nofollow">https:&#x2F;&#x2F;typeconf.dev</a> (I’m one of the founders)

A Principled Approach to Querying Data – A Type-Safe Search DSL