(Posted here from the discord to get input here)

1. An issue tracker

We need an issue tracker for various reasons, 1st being the fact that we need to know the devs are aware of common bugs.

With it Devs could set priorities for what bugs are a must fix first and what can be put off a bit

Allowing users to input things for the issue tracker that get tagged.

The Devs can share ideas for features on the issue tracker and get input.

2) Regular updates.

It is very easily coming apparent that while a lot of these new ideas being added to figgs are quite good, they're also a bit rushed and thus get half baked. They need more time in the oven and not just shot out rapid fire.

I suggest doing weekly updates, every 2 are bug fixes and every third is a new feature, that way 2 weeks can be focused on fixing new occurring bugs with a new feature and finishing off all current bugs.

Edit: Reply Clarifying

Edit: Moreso what I was originally thinking when writing this

3) A roadmap of some kind

Most of all we some kind of roadmap, mainly so we have a better understanding on what happens next, should we expect a lot of new features and potential new bugs or are the devs going to crack down on bugs that are currectly affecting the site and experiences people are having? A better expierence for the user is both features fixing and and improving some older ones before some bugs start causing the before the infestation becomes unbarable. If people keep having the same issues they'll likely get fed up with figgs due to the tedious workarounds to fix issues that can be addressed before a new update.

Edit: In referring to: In POV of the Devs "We're going to add this new feature, but also going to fix issues and bugs A, B, and C afterward. Let's make an annoucement so people understand and have a general idea so people can know we're aware of issues instead of just responding personally to every bug post." Not a "let the community decide if we fix a bug or add a new feature uwu daddy stomp all over me". I guess more so a roadmap if that's a better way to put it?

Edit: Fixed the way I worded #3

Edit: Reply with Previous #3 so you can see what it said before (I admit I sound like an ass)

Edit: Better example of what I mean

Edit to post adding new point:

4) Maybe a beta test site?

I've seen sites do this before were it's basically just for testing. So people can give feedback before the main update is rolled out, maybe it's accessible if Figg Devs create a patron, or subscribestar. That way users can support Figgs on two fronts.

Edit: I understand if some of this sounds condescending, I have no excuse. Reading it back it does sound like someone with their head up their ass is writing it and that is not the tone I meant to convey. I'll clarify what I mean in replies to comments and edit as I go along to remedy this issue. I won't edit the list that much anymore so people can see the mistake I made.