S03E33 β Time to Make the First Move
Good morning π
At the moment, I consider the current version of Appy Weather to be more of a reactive weather app. And by that I mean, it primarily clarifies the weather. With v2, the ambition is for it to be more pro-active and make recommendations based on the weather. No artificial intelligence involved but just out-of-fashion common sense. Takes much less time to code, and probably has better results (my Google Home that must be baked with AI still struggles with any simple and relevant follow-ups about the weather). To help with this mission, I need more data.
Air quality was added as a Pro subscription map layer to Appy last year, but I intend to surface it within the core experience. Custom notifications were added at a similar time with a purpose to notify you about conditions that matter to you. Although Iβm extending it to play a more active role in the foreground UX, Iβd like to compliment it with the ability to highlight when the weather is just nice. Conditions that are π Perhaps subjective, and will vary based on your climate. So this one may be a stretch to execute on a bigger scale, but Iβm wondering whether constraints can help reduce the difficulty and improve its helpfulness. For example, what if I look at 24 hours, and suggest the hour with the best conditions to be outdoors. Would still need to figure what constitutes best, but I could also let the user help me out. Finally, another example would be for forecasts beyond the next week or two. Remind me about the temperatures in the early Spring or late summer. Or being more ambitious, where in the world has the nicest weather at a particular time. I donβt want to just tell you what the weather is after youβve booked a holiday but to help you book it.
I have no idea if Iβll be able to nail any of these for the v2 launch but these are just a few of the sort of targets I have in mind for the next release and beyond.
Have a great Sunday!
Best,
Bardi