As a user of this application to manage a project I am working on, I would like to give you some constructive criticism, this application has lots of potential, but ultimately falls short. After a few attempts, unfortunately I went back to using Notion for managing the project. I would like to start with the strengths:

1. The dialog editor and the kanban board, by far, the most useful features. The visual scripting part of the dialog has lots of potential.
2. Exporting to json and other friendly formats to game engines, and programming languages.
3. The converter of the dialog into screenplay format, this has potential beyond videogame developing.

Now, here are the features that could use some work, or scrap them altogether:

1. The database-centric collaboration. This feature is virtually useless to most because installing a server to keep the project stored in a database is too much hassle for the indie developers that are likely going to use this app. I think you should scrap or abandon this feature and simply let users create a folder for each project, that ultimately can be converted into a git repository. A file format easy to keep track of in git (json, per example), could be the file that stores all the project's data. Collaboration in git is easy, you can run a git server yourself, but most likely, users will upload the project in many of the git sites available out there.
2. There are sections that are in the app, Quests, Items, Misc, that serve no purpose but text data entry, they are not different between one another, and if they are not going to be fleshed out further, they should be reduced to one single category. That will clean up the UI. Scripts and Dialogues could also benefit by being combined.
3. The UI is not particularly intuitive. To start working on a dialog, per example, you create the dialog, click on it, unlock it (the switch button to save/unlock the file isn't very intuitive), create a new dialog entry in the visual scripting board, and only then you can start writing. Streamlining the workflow will save you a lot of time having to write it down in the documentation.
4. Now, the documentation, to put it kindly, it needs work. Right now there are a couple of broken links to videos, and incomplete entries. For an app sold commercially, this does not give a good impression.

And finally, here's a feature suggestion, I think you will hit the jackpot if you consider:

• You know which is the most-used videogame project management tool, but wasn't meant for that? Excel (or Google Sheets, etc.). This is because game localization have been standardized in spreadsheets for decades. If you implement a spreadsheet meant exclusively for localization, you will spare game developers of another tool to juggle with.

I hope this critique can steer you into some solutions, but most importantly, I want you to continue working on this tool. Please don't stop development, you have something special in your hands.

Hello @harrymfa, wow! thanks for the time for providing a very detailed feedback, I really appreciate it!

About the pain points:

The database-centric collaboration.

I agree 100% that there should be another method of collaboration that doesn’t involve setting up a server. Especially git. But I don’t want to be involved in conflict resolutions/merges etc. What I could provide is some sort of “work from file” setting that would let the user use a json file as database (essentially a backup) and concurrency/conflict resolutions should be handle by the user and would be out of the scope of the app. I’m open to suggestions of any type on this subject!

There are sections that are in the app, Quests, Items, Misc, that serve no purpose but text data entry.
Well, the main focus of the app is to provide different ways for data entry, it is not necesary to use them all or to split it as presented. I agree Misc and Items might be redundant. However, I’m planning to add an option to enable/disable modules so you could theoretically remove “misc” db from showing up if you want to.

Merging scripts with dialogues might not be a good idea as they serve different purposes. (a dialogue might have a script, a script might not be a dialogue)

The UI is not particularly intuitive.
YES! I can see a major pain point in the workflow you just described, and should be refined. It’s not much but here’s a tip. If you double click in a script for example it locks for editing.

**Now, the documentation, to put it kindly, it needs work. ** No need to put it kindly, the docs are lacking and are quite useless.

And finally, here’s a feature suggestion…
This is on my radar, and it will be definitely be spreadsheet based!. I just have some issues refining the process (how to keep a “linked” translated version that updates with the original)

Thank you very much for the feedack, it is really useful!

I prefer realtime database-centric collaboration more than git, though.

At least it's more intuitive to users.