# Yahoo! Weather app -- a followup DevFeed: [Yahoo! Weather app -- a followup]() Original publisher: [Read original article]() Author: Juhani Lehtimäki Published: 2017-09-03T19:04:01Z Content type: opinion Language: en Sources: [Android UI Patterns - Medium]() Topics: [App](), [Development](), [Android]() Tags: [app](), [article](), [dev](), [developers](), [development](), [opinion](), [ux]() ## AI overview The author responds to criticism of an earlier critique of the Yahoo! Weather app and explains why the app is a useful case study for designers and developers. The article focuses on design evaluation, including the risks of using icons that differ from platform standards. ## Source excerpt Yesterday, I wrote an article pointing out issues in the new Yahoo! Weather app. To my surprise the post has turned out to be quite a controversial one. Here are some reactions to it (I won't even touch reddit comments ;) Now, before anyone tweets / messages these people, don't. They have a point (although I'm not sure if being called "pathetic" is fully justified). I appreciate (most) of these comments and I thought I'd address some of them and explain my "nitpicking" in the previous article. While getting posted (and voted up) in /r/android usually means a nice incoming traffic to the site I'd rather not see my posts there. /r/androiddev /r/androiddesign are much better places for what I write. I don't write app reviews for end users. I write for designers and developers. An app like the Yahoo! Weather is a gold mine as an example when writing about design for couple of reasons: It's done by a large company with large budget -- I think it would be wrong to do a similar detailed breakdown to an app done by a small team or an individual dev. Small teams & small budgets often create external constraints to the development and design. A large company like Yahoo! on the other hand has everything it needs. Yahoo! got close -- a detailed evaluation of an app that is so far from the goal that even multiple iterations could not take it there might not be as valuable as evaluating an app that is almost there. The Yahoo! Weather app is beautiful and has a lot of potential. That makes it an optimal example. The app doesn't have to be fully redesigned. It's a popular app -- everyone knows the app and everyone has an opinion about it. None of the critics actually told which parts they felt were the wort nitpicking in the article. However, it's pretty safe to assume that my comments about the "hamburger" icon and the share icon could easily be seen as such. So why did I choose to talk about them? Are all users now confused when using the app because the icons don't match. I'd bet m