Software has a big impact on productivity, they need to be reliable and fast. Those that require heavy updates, that have a high CPU usage and that need frequent connectivity to function are problematic for us. Much of the software on the market is designed by people living on the grid with unlimited access to internet. Tools locking up at sea, asking for a connection to continue working don't float on a boat. Adobe products are a good example, as they require an internet connection periodically for subscription validation. If away from big cities, you may open your computer in an atoll to find that you no longer have access to the tool you need to get things done. Choosing a tool that doesn't require a subscription is essential for working nomads that don't have a reliable connection.
Have a look at cpulimit to learn how to throttle running software and control the battery drainage rate.
In our first year, we struggled to download 10gb software updates on slow Polynesian internet. Processor-intensive software or apps is a strain on limited power and bandwidth, but it doesn't have to be that way. The way developers write them can affect the power consumption of the resulting product. Chat rooms and bare bones text editors aren't supposed to be process-heavy, and yet the popular communication platform Slack requires outrageous amounts of ram and CPU to function. This is because Slack is embedding the entirety of Google Chrome in their app. Making software this way is costly to off-grid users, or those on slow connections, but luckily there are many alternatives. See TinyTools and Bloatware Alternatives.
Our computer batteries should not need to grow ever larger only to support these bloatwares, nor should we need to add extra solar to power them. Just as you would look at the nutritional content of food products at the grocery store, find out how much energy your apps are consuming.