I love the idea of the Game Log when I am running fully remote sessions. My current solution set is all dndbeyond, using owlbear.rodeo for a combat map.
For players
Allow the Game Log to be snapped as a column in the character sheet view to accommodate half/split screen at the average laptop screen (1920x1080), so the snap point would be 960px wide. This would allow a player to have two windows side-by-side and have the game log visible. Or have it better integrated into the character sheet.
For DMs
For desktop/web, window/pop out the Game Log, or make it have a greater presence on the Campaign page. The Campaign page is poorly designed as far as hierarchy goes, and could have its layout better allocated to accommodate the Game Log.
For the mobile app, consider making the Game Log one of the pivots, or campaigns, and make the game log easily accessible.
Some way to send rolls from monster details to a campaigns Game Log. For example, I want to use an ability/action/attack from the Owlbear monster detail page, without adding it to an encounter for that campaign. You do have that nice little bit of UI for rolls that asks if you want to Roll to: SELF or EVERYONE, please consider a similar interaction for actions on monster pages, even if it is just to make the roll and not have it go to the Game Log.
I pixel hacked something together to show what I would love to be enable to do. Also, please note how much real estate is wasted by the encounter pages header, it takes approximately 50% of the visual real estate when you include the browser chrome. Another tip, you could have the active monster/player stats available as an accordian function, or some other dynamic element to reveal the info inline, and prioritize the actions, as that is what DMs are going to use most on this page.
I love the idea of the Game Log when I am running fully remote sessions. My current solution set is all dndbeyond, using owlbear.rodeo for a combat map.
For players
For DMs
I pixel hacked something together to show what I would love to be enable to do. Also, please note how much real estate is wasted by the encounter pages header, it takes approximately 50% of the visual real estate when you include the browser chrome. Another tip, you could have the active monster/player stats available as an accordian function, or some other dynamic element to reveal the info inline, and prioritize the actions, as that is what DMs are going to use most on this page.
Mockup:
https://drive.google.com/file/d/19w4AAfkHQTmTb-NJbhcROpvN_NJaIz_6/view?usp=sharing
Thank you for your time.