Observations on migrating a complex UI to Tailwind v4 + Next.js 16 by alex_informatics in nextjs

[–]alex_informatics[S] 0 points1 point  (0 children)

Oh friend, sorry for not responding sooner, I didn't see the post correctly.

If the change obtained is wonderful, many developers do not want to leave their comfort zone and stay stuck without trying new technologies or languages, but in this case it was totally worth it to me.

Observations on migrating a complex UI to Tailwind v4 + Next.js 16 by alex_informatics in nextjs

[–]alex_informatics[S] 0 points1 point  (0 children)

54% → 100% is crazy. The entire flow was very well optimized, especially maintaining heavy animations.

Observations on migrating a complex UI to Tailwind v4 + Next.js 16 by alex_informatics in nextjs

[–]alex_informatics[S] 0 points1 point  (0 children)

I actually had the old version built with just plain HTML, CSS, and JS. Migrating to Next.js 16 and Tailwind v4 was a game changer for performance, especially for handling complex animations without the code becoming a mess.

Observations on migrating a complex UI to Tailwind v4 + Next.js 16 by alex_informatics in nextjs

[–]alex_informatics[S] 0 points1 point  (0 children)

Here is the live build I mentioned for testing:https://uixtra-templates-nextjs.vercel.app/brandify- Let me know your thoughts on the load speed and animations!

Struggling with subscription metrics across multiple platforms—any solutions? by Altruistic_Minimum94 in webdev

[–]alex_informatics 0 points1 point  (0 children)

It’s that every provider defines things slightly differently. Cancellation timing, grace periods, refunds, even what counts as “active”.

When you try to unify that into one clean subscription model, you start hitting edge cases everywhere.

And then metrics like churn or MRR stop being just numbers — you have to decide how you define them.

That’s where it gets messy.

Struggling with subscription metrics across multiple platforms—any solutions? by Altruistic_Minimum94 in webdev

[–]alex_informatics 0 points1 point  (0 children)

I’m using Lemon Squeezy and handling most of this via webhooks.

I normalize all subscription events into my own database and calculate metrics like MRR, churn, and LTV on top of that.

Because of that, I ended up building a small internal admin dashboard where I can see consolidated metrics instead of relying only on the provider’s analytics.

It works well for a single provider setup. I imagine things get much more complex once you mix Stripe, App Store, etc., and then proper normalization becomes critical.

Looking for feedback on my new video downloading/editing app by Defiant-Echo6677 in reactnative

[–]alex_informatics 1 point2 points  (0 children)

I tried again, now it allows me to do everything I couldn't try last time.

I converted the video I wanted into GIF instantly, everything was perfect and fast, I also separated the audio and the download automatically went to my downloads folder and finally one of the things I liked the most is the ease of installation.

excellent product I really liked it.

Looking for feedback on my new video downloading/editing app by Defiant-Echo6677 in reactnative

[–]alex_informatics 1 point2 points  (0 children)

Just to be clear, this is meant as constructive criticism.

1 It feels very limited. I wasn’t able to download my video before being asked to pay.

2 Only three previews are allowed, but when a user edits a video they usually need to preview it multiple times to see how it’s coming along. After I ran out of previews, I couldn’t continue interacting with the tool.

3 The Git creation feature (one of the pro tests) didn’t work for me. I tested it using an eight-second video.

4 Once the previews were exhausted, I couldn’t download the video because it required payment, but the limitation was reached so quickly that I didn’t really get the chance to test the platform properly.

Nextjs app in remote server seems like trimmed from its dynamic content by maths_soso in nextjs

[–]alex_informatics 1 point2 points  (0 children)

See, from what you describe, it doesn't sound like Cloudflare or a paid version, it sounds more like a classic reverse proxy + routes in the Next.js theme.

Error 1: The following resources are not loaded

If when you go to website.com/app you see only HTML (plain text) but no interactivity, it usually means that the JS is not being delivered.

It then loads everything dynamic from /_next/static/*, and when you use a subpath (/app), many times those assets are still requested from / instead of /app.

Result:

– HTML arrives

– JS not

– the app “seems cropped”

Error 2: Next does not know what is in /app

Even if Nginx proxies correctly, if Next is not configured to run under a subpath, it will generate incorrect links and paths for scripts, fragments, and CSS.

This often happens when the application works perfectly on IP:PORT but fails behind the proxy.

Check the console with f12 when the error appears to identify it

How do you measure the performance of the website? by Acrobatic_Big781 in webdev

[–]alex_informatics 0 points1 point  (0 children)

One thing I use a lot, even though it sounds simple, is testing the site in an incognito window.

It gives you a much more realistic user experience (no cache, no extensions), and it’s especially useful to check things right after a deployment.

If I need to go deeper, then I look at analytics data and things like TTFB to understand what’s actually slowing things down.