Devs make things they feel like making, or things they think the world needs.

What kind of an app (web, desktop, or mobile) would you want to see? What is something you wanted or needed for a long time that simply isn't there, or there but so bad with X that you can't use it?

Alternatively, what is a common problem that could be solved with software but hasn't been yet, or at least not effectively?

Leaving this vague on purpose, to let Tilderinos express themselves.

I promise this is a genuine question and not a Windows hit piece.

Every Windows computer I've ever had has slowly gotten laggier over time until my impatience has forced me to reinstall the OS to get the speed boost that comes with a fresh copy. In the schools I've worked in, computer labs and carts full of Windows machines have slowly sunsetted, becoming wholly unusable over time. I think Chromebooks have taken over education in part because they have a snappiness to them that sticks around for a long time, unlike the decay demonstrated by Windows computers.

In my current job, I was issued a Windows computer and a Chromebook at the same time, when I was hired. The Chromebook is still chugging along just fine, but the once fresh and quick Windows computer is now ramping down. I know it's not because of startup or background programs latching on over time because I don't have admin rights and thus can't install anything! I'm not a power user either. I really only ever run a browser with minimal tabs, along with the very occasional instance of office software and/or PDF reader. That's it. And what used to be instant and quick is now like... trudging... through... sludge...

Is there some fundamental design flaw in Windows? Am I finding a pattern where none exists? Do I not have enough experience with other OSes to know that this is true for them too? I'd love someone's insight on this topic.

Input wanted for an article.

Let's say that your company is considering the purchase of an expensive new application to help in the company's software development. The demo looks great, and the feature list makes it sound perfect for your needs. So your Management arranges for a proof of concept license to find out if the software is worth the hefty investment. The boss comes to you to ask you to be in charge of the PoC project.

I'm aiming to write an article to help developers, devops, and testers determine if a given vendor's application meets the company's needs. The only assumption I'm making is that the software is expensive; if it's cheap, the easy answer is, "Buy a copy for a small team and see what they think." And I'm thinking in terms of development software rather than enterprise tools (e.g. cloud-based backup) though I suspect many of the practices are similar.

Aside: Note that this project is beyond "Decide if we need such a thing." In this scenario, everyone agrees that purchasing a tool is a good idea, and they agree on the baseline requirements. The issue is whether this is the right software for the job.

So, how do you go about it? I'm sure that it's more than "Get a copy and poke at it randomly." How did (or would) you go about designing a PoC project? If you've been involved in such a project in the past (particularly if the purchase wasn't ideal), what advice could someone have given you to help you make a better choice? I want to create a useful guide that applies to any "enterprise-class" purchase.

For example: Do you recommend that the PoC period be based on time (N months) or workload (N transactions)? How do you decide who should be on the PoC team? What's involved in putting together a comprehensive list of requirements (e.g. integrates with OurFavoredDatabase, meets performance goals of X), creating a test suite that exercises what the software dev product does, and evaluating the results? ...and what am I not thinking of, that I should?

Grandma is understimulated in assisted living, and while Mom is looking into ways to either bunk with her, or drag her back to our place, I'm exploring other options. Her apartment does have wireless internet, so we could set up some sort of telepresence or video calling device, but even something as simple as a Relay or a KC2 isn't great, because it loses power, and needs to be explained to her.

I'm thinking that we might have better luck with a Tablet or a PC solution, and I do have a Kindle Fire (5th Gen?) and an off brand Windows 10 tablet around, and I am open to a Pi Project or speciality devices, but it has to be simple enough to plug and play, and the dream would be if it could start a video chat without the receiver having to pick up, or at least as simple as a nurse being able to come in and start a call. Any suggestions?