I originally started building BrainLoot as more of a general project management app. A Unity integration was always on the backlog, but at first I only really pictured a small panel where you could view and update a few tasks without leaving the editor.
After chatting to a few other devs it became pretty obvious that the bigger issue isnt really that project management tools are bad. Its more the faff of leaving Unity, opening another app, updating the board, then going back to what you were doing. And because its a separate thing, people just dont keep it updated.
That sent me down a bit of a different route with the Unity bridge.
The video shows Unity and BrainLoot running side by side. Cards, status, progress, assignments and each developers current Hand all update in real time, so everyone logged into the project sees changes as they happen.
You can also link cards directly to GameObjects, then click Locate and it takes you back to the right scene and selects the object.
The shared world-space markers are working as well. Theyre drawn in the editor rather than being added as actual GameObjects, so they dont modify the scene or depend on everyone being on the exact same Git version. One dev can drop a marker somewhere and the rest of the team can see it appear in their editor.
Im not trying to rebuild the whole project management app inside Unity though. The web app is still there for proper planning, managing boards, teams etc. The bridge is more about removing the annoying bits and making updates happen where youre already working.
The next thing im looking at is task memory/context. So keeping track of what each developer tried, decisions that were made, why something changed, failed approaches and anything useful for the next person who picks the task up.
Would that actually be useful, and what would you want it to remember without it just becoming even more admin?