Is there any more complex app to see?

[frederikhors]

I saw the famous video https://www.youtube.com/watch?v=3GObi93tjZI about SaaS htmx app (from React).

But honestly that app doesn't seem so complex to make, also because the parts where they use htmx are few and "simple".

Is there an example of some more complex app out there?

[Telroshan]

Don't want to sound like self promoting, but I'm making zorro.management which is extensively using htmx.
I have additionnal custom JS to add UX where appropriate (drag'n drop, mood boards interactivity in general).

Though, that's the neat part ; it's always "simple" to use htmx, so I wouldn't expect to find particularly intricate htmx usages in Zorro, despite having ~1200 hx- search results in the project's codebase.

[Telroshan]

Hey, finally getting to it @frederikhors
Thanks for the links again, really helpful
I'm trying to investigate first without using a service worker.

• So htmx fires an XMLHttpRequests when meeting the trigger criteria
• I answer on the backend with, say, Cache-Control: max-age=1, stale-while-revalidate=300 for a task's details tab. I can indeed observe an instant tab opening while it's cached when closing the tab and clicking again on the same task. I must admit it's a pretty smooth UX there
• I can see in the Network tab that the browser automatically fires another request right away to update its cache
• So, I may be wrong there, but it seems to me that we shouldn't need a service worker, given that the browser already takes care of that making a revalidation request depending on the Cache-Control value, and updating its cache
• If htmx could hook to that revalidation request the browser automatically makes to update the cache, htmx could then come back to the first request it made (that returned the outdated cached response), and update it with the up-to-date content retrieved in the meantime by the browser
• Though, I still haven't found any way to bind a listener or anything similar to that browser's automatic revalidation request, do you know if and how one could do that? Or is precisely because we can't do that that you're suggesting a service worker here?

Being able to rely on the browser's native features would be neat, would be sad imo to have to implement our own caching strategy with a service worker when the browser could already handle it

[frederikhors]

I'm glad (or not so?) that you have the same doubts of mine.

[davidwilde]

Hey there, I'm running into this exact scenario and I'm thinking of building a HTMX extension called swr to see if this could be resolved this way.

If either of you would like to help with building / testing this then get in touch

[frederikhors]

I will be glad to, @davidwilde.

Plus, this swr can help for something like: https://www.reddit.com/r/htmx/comments/1f9vcqu/is_this_pattern_possible_with_htmx/ ?

[davidwilde]

Nice! I think I'm in the same position as @Telroshan in that I can see that the second network request goes out but I'm not sure how that is handled by xmlHttpRequest. I've had a brief look at useSWR (which is how I know about stale-while-revalidate) and notice that under the hood it is using axios so I'm wondering if a bit of this logic exists in axios itself or in the useSWR library.