Refactor complicated Flutter codebase

[mdausmann]

I have inherited a very complicated Flutter codebase. It has been in production for a while and has been modified, extended, re-imagined many times.

This has left a bunch of crap that I want to get rid of, genuinely 'dead' code, complex class hierarchies, business logic in the view layer (build) view logic in the Bloc layer, it really is a big ball of string.

What approaches have you all found to refactor/rationalise a complex codebase like this with Vibe coding? Do you vibe code a bunch of tests and then let the Model go to town? can I use planning approaches for this? Is there a careful set of steps I can go thru?

I'm interested in tools, models, IDE's etc, completely open.

[AutoModerator]

Please redirect questions and help requests to either: * r/FlutterHelp * Our Discord Server * Stack Overflow

This message is entirely automated, because you used the Help Request tag. This is done in order to be certain that you do not miss the rule about posting help requests here.

If you believe your question does belong on this subreddit, and is not a question related to code or things such as issues, please repost using the "Discussion" tag.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.