My own Virtual Tabletop? Really?
I build applications like Star Systems or HMK Toolkit to help me run role-playing games. During a game, there is a lot going on, and I don't like to have to search for information. For example, when I need the stats or skills of an NPC, looking through the adventure for these stats will often take time and make me lose my current page on the adventure. I'm also bad at taking good notes during a game session. Things like tracking the time and date, damage, ammo, etc. I used to scribble notes all over the place and lose track.
But more importantly, all these little things occupy my brain, or I should perhaps say “clutter” my brain. They use up my mental CPU, which I’d much prefer to use for improvising and role-playing and making the game fun for everyone involved.
So anything I can build into an app to help me with all of this is something that I then don't have to worry about.
The problem is that I have to use a VTT to run a game online. And setting up a VTT to run a game feels like doing everything a second time. I need to learn the system’s implementation (if there even is a system), re-create all the PC and NPCs, create the scenes and add the walls, adjust the scene’s grid, create all the items and skills, etc.
So I realized recently that this was the main reason why I procrastinated on actually running a game. All this extra work, unconnected to the tailored tools I had made for myself. That’s when I decided to build myself a VTT within Star Systems.
The first thing I decided was that I wouldn’t bother with browser support, login credentials, and automatic fog of war, also known as “token vision.” Token vision is fun as a player, but it’s a lot of work for the gamemaster because you need to define walls, doors, windows, etc. As someone who has used FoundryVTT, both as a gamemaster and as a player, I know how cool it is to use as a player. However, I also know how confusing it can be for the less technical players, and how disrupting it can be when you have to explain to a player how to use the VTT instead of how to play the game.
So, both because I didn't feel up to the challenge of handling internet connections (and I don't like javascript), and because it's much simpler as a referee, I decided to build what I call a "one-way" VTT. The players can then concentrate on playing the game and everyone sees the same information at the same time—just like they would on a table like we used to do when we played in person. The only difference is that they can’t directly control their tokens.
I let my players roll their own (real) dice if they prefer (most do), but they can also roll in Discord. The automation of combat that a VTT with a system would offer them is replaced with the automation that I build into my app. I can just give them the sum of the modifiers that Star Systems tells me automatically. So, instead of asking me which button to press in Foundry, they tell me what they want to do, and I can tell them what to roll to see if they succeed. Now that feels like playing a role-playing game!
In terms of scenes or battle maps, as people often call them, I can set one in under a minute. Screenshot the map in the adventure and save it somewhere. Then add a new scene in Star Systems and select the image I just saved. Open the scene in the Referee panel, choose the “measure tool,” drag across two lines, and say what that represents as a dimension in metres and I’m ready to go. Drag a traveller and its token is created automatically from the portrait.
It's so refreshing as a referee. I can spend less time fiddling with Foundry and more time thinking about the game!
Now, building a VTT hasn't been an easy thing to do, of course. It was quite a lot of work to implement to be honest. A lot of testing, designing, and refining. And I am sure there will still be many modifications and improvements down the line, but I can honestly say that I am very proud of this first version of the VTT.
An argument for Traveller in particular
All of this is especially true for Traveller. Traveller has many sub-games, let's call them game modes. In general, traditional VTTs only support one of these modes: the scenes or battle maps. What happens when you want to show your players the star map, handle trade, or run a space combat?
In Foundry there is no mode for checking the star map and looking at routes between star systems. There is no trading mode where the players can see the available cargo. There is no space combat mode. You end up sharing your screen, pasting images into a scene, or just describing everything out loud.
That's why I made five VTT modes in Star Systems, one of which is the scene (SCN) mode which is what the traditional VTTs usually offer.

Travel State
The first mode shows static backgrounds with dynamic information on the front. These are meant for when things happen in the theatre of the mind: the ship is in jump, the travellers are walking through the starport concourse, or they're haggling with a broker in a dingy office.

The various states give the players context for where they are, and the information keeps them updated on their specific location, the date and time, what each character is doing, and information on their shared credits and their ship's manifest.
This is the mode I use the most. It's what's on screen when nothing else is, and it means nobody has to ask "what day is it again?" or "how much money do we have left?" ever again. Since Star Systems already tracks all of that for me, the players get it for free.
Star Map
The second mode shows the star map. I can show the players where they are (the hex with a golden border), where they've been, and the routes they could take with their ship's jump rating. The map is live and I can pan and zoom and point out star systems.

In a traditional VTT, I'd have to export a map from a site like TravellerMap, upload it, and then keep it up to date myself. Here, it's the same map I already use to prepare the game, so when the travellers plot a course, they can actually see the options and argue about them among themselves. That's the kind of discussion I want at the (virtual) table.
Trade
Trade is a big part of Traveller, and it's also the part where my players' eyes tend to glaze over when I read a list of numbers out loud.

The trade mode shows them what's available at the current world: cargo lots, freight, passengers, and prices. Star Systems does all the DM calculation by the traveller's skills and the system's trade codes. The players make the rolls and I enter them in Star Systems which then projects potential profit or loss based on those same skills and the trade codes of possible destinations. The players see the results on screen. They can decide what to buy and what to sell while Star Systems handles the bookkeeping, adding campaign notes automatically, and the ship's manifest and shared credits in the Players' Panel are updated automatically.

It turns trade from a referee monologue into a group decision, which is how it should be. And I don't have to take notes or spend time looking up trade code modifiers.
Space Combat
Space combat in Traveller doesn't really happen on a grid. It happens in range bands, with crew members at their stations doing different things each round. Trying to fake that on a battle map always felt wrong to me.

The space combat mode shows the ships involved (at least the ships the players detected!), their distance and bearing. Each player can see where their character's duty and what are their options for that duty in the current combat phase. I ask them what they want to do in each phase, tell them what to roll and they see the results live. I run the combat from the referee's Space Combat panel (below) and the Players' panel is updated live.

The scene mode
Finally, there is the scene (SCN) mode, which is the one that will look the most familiar to anyone who has used a VTT. It's the battle map: an image, a scale, and tokens.

As I explained above, setting one up takes less than a minute. There are no walls to draw, no doors to place, and no lighting to configure. I move the tokens based on what the players tell me, and I reveal what they can see by removing the fog, like a referee would on a real table by adding tiles or drawing on a mat.

I get a number of tools to make my life easier, like the "move aid" which makes tracking movement allowances a breeze. Drag and you see a range overlay. Add segments and press option for difficult terrain (see the second segment marked 'x2' on the image below). This is a 3-minor actions move.

And because the scene is part of Star Systems, the travellers on the map are the same travellers I track everywhere else. Their portraits become their tokens, and their stats, skills, and damage are right there in the Referee panel when I need them. No duplication, no second copy of the characters to keep in sync. When combat starts I open the Combat Round Tracker and I tell them the modifiers to their roll (Star Systems automatically tracked the dodge DM-1 in the picture below), enter what they roll, etc. I can apply the damage they roll to NPC automatically, etc.

Conclusion
Is it a full replacement for Foundry? For me, yes it is, at least for when I referee Traveller. Is it better than Foundry? It depends on how you see it. For scenes: clearly no it's not. The player's experience is different. But for a big part of Traveller which isn't personal combat, I would argue that it's better. It's a tool built for the way I like to run Traveller: the players play, the referee referees, and the app takes care of the clutter.
Most importantly, it removed the main reason I kept putting off running games. Now I just have to actually run them.
Star Systems is a free macOS application. Check the extensive online documentation.