at a game studio of 300 i would wander amd chat with the various non-coder teams and just watch their workflows. for the tech artists a big blocker was gui access to enums in shaders (custom engine). i just set several of them up to compile the engine and taught tyem how to link enums to the editor gui, saved them many weeks of wait time. saw the lighting bake loop would take 1 year to run fully and a local test loop was 8 hours. asked my boss for time and rigged up a cluster of 64 ps4 dev kits and brought that down to 45 minutes, going from less than one local iteration a day to 9, and less than one a year to 3 a week for full bakes (cluster would bake when it wasnt helping am artist).
at super large mega corp i do similar, constantly meeting people for coffee and understanding more than just my cog. Eventually I got good enough at it and a reputation for improving things that I just get pushed/pulled at problem/opportunities areas, but you have to work up to it.
while none of this is doing a startup, if youre not curious, youll never see the myriad of things that could be improved with software, nor will many non tech folks, or really anyone who doesnt think "outside the box" as the olds say. challenge for devs is understanding where that tech is worth it and how to sell it, and not become that angry dev who is just yelling at everyone and politics for not taking every one of their half baked ideas as words from on high.
An example from my day to day in a large corporation: we have to enter time weekly: how much time did you spend on project X, Y or in training/meetings/etc. Sure there is software that does this, but it's terrible There are many issues with it that should be trivially solvable.
Now, I will admit that time tracking software is a huge field with lots of strong competition, so this may not be a field you'd want to enter, but it's an example of the problems you would come across during an average workday that are ripe for better solutions.
Try meeting people not in your field. Yes, it will take effort. Yes, it will be uncomfortable. Because of those challenges, fewer people have explored that space - so there are still fertile grounds for new products.
Was the original remote app enabled? If not, now you have a potential product for those people who would rather use an app than the manual remote. Are spare remotes hard to get or expensive? There's another market that might want to buy from you, especially if the AC unit that is old or obsolete.
Spare parts/retrofits with new features is big business. There's a good chance that if you dug into this particular problem you'd find that it could be profitable. Not quit-you-day-job profitable, but at least enough to bring in a few extra $k per month.
My point was that this does solve my problem but it's an incredibly niche problem for an even smaller niche market. The owners of this AC from the same unknown manufacturer, that either can't find a spare remote or want to make it wifi enabled. It's insanely specific, isn't it? Let's not fool ourselves, writing the software is the easy part and fairly inexpensive when you can do it yourself, get a cheap stm32 board and flash it. Manufacturing on the other hand is a whole different ball game and honestly I can't justify the work of developing, manufacturing, distributing and dealing with taxes at the end of each month, all for 300 bucks tops(I'm probably far too optimistic).
edit: esp32, not stm32(I'm mostly playing with stm32 lately).
> an incredibly niche problem for an even smaller niche market
These are my favorite because no one "big" wants to get into them. I make a device that converts signals from heavy machinery that uses a specific type of almost-obsolete sensor to let it use a modern control that you can buy off the shelf. A friend of mine used to have a nice side business (was full time for a while) selling a replacement timer for a specific type of industrial printer.
I like markets like that. The biggest problem I'd see in your case is that it's a consumer item, not industrial. Most customers just don't want to spend a whole lot unless they have to.
Resptfully disagree. There are a lot of non-trivial problems that do not have good solutions. If you look for niche manifestations of hard problems, you can both find something with appropriate scope AND a good value proposition. You also don't need to solve problems, just make them better/easier.
Agree with this. As they say - necessity is the mother of invention. A lot of the episodes I listened to on the Podcast - How I built this with Guy Raz - were about people getting frustrated with a problem they faced on a daily basis and deciding to fix it (usually starting quite small).
2) >>> This is probably why there are so many more startups pitching development tools than, for instance, something to make the lives of truckers a little easier. <<<
This makes sense if you're a developer or work in software. Eg, I'm a Product person who built tools on the side to scratch my itch. My platform was Google App Engine (GAE). When the GAE GUI was deprecated, I realized that I really found a GUI much more convenient and so built - https://nocommandline.com and in the process fixed stuff I didn't like about the old GUI.
I think the trick here is to set right expectation i.e. recognize that not every idea is going to be a Unicorn or a big business. It could remain 'just a side project' or turn out to be something that just brings you extra income (pay your rent, weekly gas bill, etc).
The best part (and the part relevant to your comment) is that this just opens a Chrome window and you can open (cmd-N) as many windows into the same slack team as you want, and it behaves like you expect a Mac app to behave: cmd-tab goes between teams and cmd-backtick goes between windows of a single team.
I gather that there are some Mac apps or extensions or something that let you gather windows of _any_ app into tabs, so you could likely use one of those here to get tabs instead of windows.
Supposedly Chrome is getting rid of support for Chrome Apps, I think that's what these things are called (?). If so, I'm going to be impacted when it finally goes away.
Threading suddenly works in a non-stupid way, search suddenly works, and you can manage your own windows.
My thumbrule: 1. Pick a market that already has money-making companies. If you can beat them by price & quality, even after considering the first-mover advantage - go for it.
2. [From pg's essay] Just experiene more in life, with different people facing different kinds of problems from different sectors. That's a sure shot way to eventually run into a market with less competition.
- http://paulgraham.com/startupideas.html
This is probably why there are so many more startups pitching development tools than, for instance, something to make the lives of truckers a little easier.
If you work as a regular engineer, you must come across dozens of daily problems any of which are not properly solved by your current tools. Even simple things like following up consistently, or checking to see if someone responded to an email to a third party etc
Addendum: In response to many comments, I should add that this method is not supposed to guarantee you a good idea, but is a source for ideas to filter, refine, develop or abandon.