You might not use that many features, but you can’t know what other users and developers might need. For some, the built in multiplayer and voice system might be a make or break feature, and for others it might be remote play together.
With how many users, developers, and features there are, it’s not enough to start replicating a couple features and promising more later. When is the last time you bought into a promise and weren’t disappointed? If you want to be serious competition, you better give it your all.
I can’t know, of course, but it is possible to start in one area to an MVP to a good chunk of people and add features by requested priority. Trying to do all of it all at once so feels like the wrong approach (with 20 years of software engineering and some project management experience)
I mean we are talking about trying to overthrow THE gaming giant. Smol MVP and expanding from there might be the right approach most of the time, but in this case you run the risk of becoming Epic 2, the store that took several years to add a shopping cart. And in that time where you’re expanding you’re in that awkward space where people would have to use both Steam and your system.
So I think it’s better to come out of the gate swinging. Obvs you should run lots and lots of internal tests, but as soon as you release to the public, you should be able to replace Steam for lots of people.
I could be wrong, but I rarely am :)
You might not use that many features, but you can’t know what other users and developers might need. For some, the built in multiplayer and voice system might be a make or break feature, and for others it might be remote play together.
With how many users, developers, and features there are, it’s not enough to start replicating a couple features and promising more later. When is the last time you bought into a promise and weren’t disappointed? If you want to be serious competition, you better give it your all.
I can’t know, of course, but it is possible to start in one area to an MVP to a good chunk of people and add features by requested priority. Trying to do all of it all at once so feels like the wrong approach (with 20 years of software engineering and some project management experience)
I mean we are talking about trying to overthrow THE gaming giant. Smol MVP and expanding from there might be the right approach most of the time, but in this case you run the risk of becoming Epic 2, the store that took several years to add a shopping cart. And in that time where you’re expanding you’re in that awkward space where people would have to use both Steam and your system.
So I think it’s better to come out of the gate swinging. Obvs you should run lots and lots of internal tests, but as soon as you release to the public, you should be able to replace Steam for lots of people.
I could be wrong, but I rarely am :)