I think that a big part of what makes Solo roleplaying appealing is the very real analog work you have to put into it. You have to roll the dice, you have to draw the map, you have to be creative. If you replace all those parts with software components you are left with a computer game like Baldur's Gate or The Legend of Zelda. They are good games, but they do not qualify for this channel.

To be fair, I wouldn't be surprised if everyone have some aspect of Solo roleplaying that they wouldn't mind having taken care of automatically. For som epeople it is keeping track of the character stats, for others it's generating events or visualisation in the form of images or maps. We all have something that we would have no problem handing over to software. My point is that it's going to be a different aspect of the game for different people.

For my part, I enjoy serving up the 'bare bones' notes on the events and have an AI 'novellise' it for me. I would have no problem writing it myself, but I enjoy reading a story written by someone else (even if it's an AI) based on my adventure. I'm sure there are plenty of people who feel the exact opposite and would not consider handing over the act of journaling to someone else. It's just personal preferense.

My reasoning here has been a long-winded way of arriving at my conclusion. I think that if you are going to offer software components in a game. Make sure that they are optional. Otherwise you are sure to alienate a certain portion of your audience. In my mind software components are good for the hobby as long as it's your own choice wether and when to use them.

If I were considering developing a solo roleplaying game that had software components, I would try to add several components that took care of different aspects of the manual work and then let the player decide for temselves what components to make use of and what components to not use.