3 ms·

Funny, I read the author as saying there are not enough ’new’ ideas. I find the drive to make it new is a curse on mobile. Many apps have betrayed me (1Passwor

Funny, I read the author as saying there are not enough ’new’ ideas. I find the drive to make it new is a curse on mobile. Many apps have betrayed me (1Password) or threw away best features (WeatherUnderground) or just lost touch (Transit) when they update their products with new features. IMHO, if you want to make something ‘new’, then take a page from Hollywood and call it ‘2’ or ‘revenge’. Interesting a later thread about new hardware and old software seems to have the same problem—companies won’t support old software with only a small fraction of users. https://news.ycombinator.com/item?id=35339006 https://news.ycombinator.com/item?id=35339006

throwaway936x 4y ago
> I find the drive to make it new is a curse on mobile. Many apps have betrayed me (1Password) or threw away best features (WeatherUnderground) or just lost touch (Transit) when they update their products with new features. I think this is unfortunately a "natural" progression for companies who focus on growth. In the beginning, they are a small team that has limited resources and is forced to focus on what matters. Once they grow, they start multiplying the team sizes, introducing new levels of management and hires experienced product and tech people. Often for no other reason that they need to grow, and that means more resources. The new hires have to justify themselves and need to find work to do. Product people have to make visible changes to signal their worth to upper management, while developers invent new problems to solve so that they rewrite the platform to $current_hype and add complexity and unnecessary scaling.