|
|
|
|
|
by theshrike79
17 days ago
|
|
If you never ship, how can you iterate? Do you spend weeks running benchmarks and optimising your code without asking/observing a single actual user whether they care if that bit is fast or not? Or would it be more efficient to ship something, gather data and iterate where relevant? Because if you're not doing that, I can guarantee other people are. Sadly being the first and moving fast (adding features as users request them) is in many cases better in the mobile market than having the snappiest app with zero memory leaks and excellent battery efficiency. The whole Turkish mobile gaming industry works on this principle, they ship like crazy and iterate quickly to see what sticks. |
|
Our discipline has swung way too far in this direction. The useful insight of "watch your users use your product -- you will always be surprised about something" has turned into "you cannot possibly have any vision or produce a useful product without constantly probing your users".
A/B testing, design by committee -- it reeks of cowardice and produces garbage. It reminds me of an SNL skit where politicians in a debate were able to see real-time social media responses to their talking points, and they immediately started playing a sort of "hotter/colder" game, changing their politics to try to get the graph to go up.
I promise you it's possible to just have an actual vision yourself. Yes, talking to users will surprise you, and it's important. But the idea that you cannot possibly iterate without shipping code is way, way too extreme.