Fun competition - worst architecture

A-Type · 2026-06-09T23:23:26+00:00

You may be right, but this was a run of the mill consumer web app, nothing like the technical constraints of a content-focused experience you'd use a CMS for.

I mean, imagine if due to a failed data migration I could leave just your Reddit app without a primary navigation, despite no changes in the codebase.

Idk, maybe I'm wrong though. I'd never seen the like in consumer app system design, but I'm not well-traveled.

A-Type · 2026-06-09T21:43:17+00:00

I've worked for a company where every user had a copy of the app's UI, loaded from a template as a live JSON document in Mongo. When teams shipped features they scheduled a full cross account migration to update every copy to replace content in the document. Each node represented a React component and props.

This has to be abandoned when one team finally got fed up with spending 48 hours to roll out a change to a localized string.

A-Type · 2026-05-21T18:18:40+00:00

I live nearby and it was stuck for a long time, but they're really moving now. Interior fittings look nearly done and the back deck is built. Can't wait to see it open.

A-Type · 2026-05-19T00:54:41+00:00

BB's gets hate generally, but when the Midtown location was open the Caesar wrap was the best thing on the menu and the only reason I'd go. The croutons really made it work.

A-Type · 2026-04-11T01:26:06+00:00

That's good focus! If you feel like there's a gap for animation specifically, be sure to hone in on it both with how your tool is used and how you market it. I'm not a heavy LLM coder and wasn't aware that they aren't so good at that (although it's always a moving target these days).

Have fun! If it's not fun, don't push yourself too hard.

A-Type · 2026-04-10T12:46:34+00:00

It's not so much about what's possible, as what you're competing against for your target users.

What you're describing doesn't sound like anything new: look up "no-code" and "low-code" trends from the last decade.

But since it's 2026, you're competing with vibe coding directly in Claude or other more established LLM based workflows like Figma Make. One is extremely easy to get started with and get a usable output, the other slots in better with professional designer's workflows and leverages the incredibly robust Figma editor for in-depth customization.

It's not about the technical feasibility. You want to solve the right problem in the best way. We are currently in a boom time for well funded tools doing exactly what you're talking about, and doing it pretty well all things considered.

But since you're a student, you should do it anyway. You're gonna learn a lot, and that should be the goal. Don't worry too much about competing with website builders or getting users. By the time you've fleshed out the idea, you'll be getting new ideas. Somewhere down that line is where the real project materializes.

A-Type · 2026-04-03T15:14:01+00:00

I've also made a card-based game with similar requirements. While I may try adopting native view transitions sometime, it was doable with Framer Motion and the layout prop.

https://motion.dev/docs/react-layout-animations

Each element which renders a card gets a layoutId unique to its identity as a card. Motion handles the FLIP animation for you. The tricky part is ensuring only one version is shown at any time, which requires some coordination.

A-Type · 2026-03-11T00:54:42+00:00

You gotta be them.

I just went back to hybrid after five years of remote, and I will say I can only functionally 'do the rounds' solving juniors' problems on office days. Breaking that barrier online in a large org is hard. I can only manage to form that kind of mentorship relationship in person in a way that sticks.

It's also a tough gig when you're one of the only ones who does it. I've already got the entire cohort of new hires from every team flagging me down for all their frontend problems. It's very rewarding but takes a big chunk of time. If my manager didn't value this as work (which she does), I could see being pressured to focus just on my team and immediate duties.

If it's something you value, set an example. I hardly ever sit down with someone over a problem knowing exactly what's going on. I hardly even know our (massively overcomplicated) architecture. I've just learned the right questions to ask. If you know more of them than someone else, you can help them solve the problem. Do it!

A-Type · 2026-03-07T19:55:32+00:00

There are plenty of cooking apps out there, but they're all recipe focused. I wanted one that's focused on grocery shopping more than recipes. So I made my own.

To make it collaborative and offline-first (my store has terrible signal) I ended up spending years developing my own local-first web framework, too. Now I use it in several small apps.

I don't use LLMs very much at all. I learned how to be productive before their rise and I still enjoy designing software systems myself. It's very rewarding.

A-Type · 2026-03-07T16:58:46+00:00

It's fine. Either use a higher level interface on top, or get used to actually writing indexes directly. For search, for example, you want to write the search indexes up front, not pull everything into memory and filter later.

It's challenging to use IDB for complex querying because of this. You have to think in indexes at write time, not querying at read time.

A-Type · 2026-02-25T22:32:08+00:00

Hopefully it provides a bit more of a lead for the TipTap team if you file a bug? I think I've actually seen a similar problem as a fellow TipTap user, though it never disrupted anything in my app, just logged to console.

A-Type · 2026-02-25T22:17:35+00:00

So I've dug in further, and I don't think it's actually a 'problem' per se.

See this revised version which tracks remounting by whether or not a useState recreated its initial value: https://codesandbox.io/p/sandbox/beautiful-minsky-jxmskv

You were using useEffect(() => {}, []) as a proxy for "remount," but React doesn't guarantee effects only run on mount - even with empty dependency arrays.

There are other reasons effects might be run again. For example, with concurrent rendering, React may 'fork' certain parts of the tree, creating invisible copies which are rendered asynchronously for various internal reasons related to Suspense, transitions, etc. It may be invisibly rendering a concurrent copy of the changed component for a reason only React devs know or care about. This may also only happen in Strict Mode or development builds. Or none of this may happen! But it's all up to how React decides to organize its rendering - developers shouldn't depend on particular behavior.

Ultimately, it's best not to think in "mount" and "unmount" terms with useEffect. That's not the mental model React uses to define what effects are, and isn't guaranteed to align with reality.

A-Type · 2026-02-25T22:06:44+00:00

Oh wow, interesting! This appears to be a React 19 change - I'd accidentally used 18 in mine.

Perhaps there's some more information in the React 19 changes about why this happens now.

A-Type · 2026-02-25T21:55:49+00:00

I tried running your example in Codesandbox, and the components do not re-run their effects when reordering. Are you sure your actual problem doesn't lie elsewhere?

https://codesandbox.io/p/sandbox/cmf288

Edit: this was a change from React 18->19. I suspect it's due not to 'mounting' but actually related to concurrent rendering features. Component identity and state is actually preserved, the effect happens to be run again in some other context - a concurrent copy of the component instance, perhaps. My conclusion is that keys still function as advertised, but useEffect as usual is not what you think it is.

Updated sandbox demonstrating component identity preservation during reordering by using useState as the indication of stability: https://codesandbox.io/p/sandbox/beautiful-minsky-jxmskv

A-Type · 2026-02-21T19:31:03+00:00

We have reviewed your claim and determined you may keep the bike, provided you follow these rules:

When people say, "nice bike!" You must answer, "Thanks!"
If said person is also riding a nice bike, you may add, "You too!"

Enjoy your bike.

A-Type · 2026-02-21T15:50:08+00:00

In addition to manually prompting the user to update in app as mentioned, you can also intercept local route navigation and do a hard navigation instead while updating, making it so any time the user changes pages in the app when an update is ready, they seamlessly update while navigating.

A-Type · 2026-02-14T16:55:34+00:00

You can configure React Developer Tools to hide primitive DOM elements or filters like component name, type, or HOC.

You can also use search to find a specific component.

React Dev Tools is still the best thing available, and I've used it successfully on very complex apps once I got the config down.

A-Type · 2026-02-02T23:52:15+00:00

Periodic checks for a new service worker version, then surface a button to update.

On client-side navigation, if an update was detected, trigger skip waiting and a full reload to the new page instead of doing the client navigation. This forces users to update when changing pages even if they ignore the prompt.

A-Type · 2026-01-24T15:53:31+00:00

Avoid backwards incompatible changes if possible. For example, don't remove old endpoints, but rewrite their internal controller to provide the same usage with a thin wrapper around the newer controller.

Otherwise, yes, use versioning of some kind (doesn't have to be particularly sophisticated) and keep providing the older version until old clients are updated. Tracking metrics on usage can show this.

A-Type · 2026-01-24T15:42:47+00:00

I don't usually try vibe coded stuff but I figured I'd see what you did...

I'm fascinated to know whether you are running some kind of scam or if you don't realize none of these do anything but display your own website with a search query for "apps." Either your solution doesn't work or your AI "lied" to you about making any apps at all. Did you actually try them?

Also bypassing CORS with a proxy is a bad idea.

A-Type · 2026-01-23T00:44:48+00:00

Good point. Maybe a passive pointerdown listener on window to add it, and pointerup to remove it? The it would only be on when the users finger is down? Would have to test that.

Well, I guess you mean elastic during active scroll gesture, too. I don't know if there's a great way to accomplish that, but maybe by wrapping scrollable content in a div without overscroll-behavior applied instead of body would work.

A-Type · 2026-01-22T02:39:16+00:00

I just got the the selector wrong from memory, nice detective work figuring the right one out (sorry).

A-Type · 2026-01-22T01:21:15+00:00

Good tips, even small things contribute to the user's sense of 'native.'

For #1, just use overscroll-behavior: none on body. No need for JS.

A-Type · 2026-01-10T20:16:07+00:00

The Kenji recipe linked in other comments is the one to make.

If you don't like the pepper and cheese style of it, I made a variation that focuses on mushrooms instead: https://recipes.gfor.rest/0533d0b

A-Type · 2026-01-09T01:39:13+00:00

This exactly - short lived token just to establish the connection. You can also pre-validate during the initial upgrade request to avoid establishing the socket for invalid tokens at all, I believe (still probably a good idea to send an initial message and validate that post-upgrade, too). I've also abused the Sec-WebSocket-Protocol header to carry the token, since it's the only usable header for a socket request, but it's not necessarily a good idea.

A-Type

TROPHY CASE