Start with the UX and work your way backwards. I don't like it from an engineering perspective, but it's the only way to go to build products.
Users just do not care what kind of horrible kludge is running behind the slick UI.
Start with the UX and work your way backwards. I don't like it from an engineering perspective, but it's the only way to go to build products.
Users just do not care what kind of horrible kludge is running behind the slick UI.
Since neither the user nor the programmer knows the right answer, we have to work iterations in. Each iteration is followed by feedback. Given how often we end up being completely wrong, it is best to get to the first feedback as quickly as possible.
This! Back-to-front is a good way to build a scalable, performant, cleanly designed software. Front-to-back is the only viable way to build a usable product.
> Users just do not care what kind of horrible kludge is running behind the slick UI.
For 99.9(9)% of users, the UI is the product. Even those who do know what "back end" means, do not care.
Front-end is pretty much as close to the user as you can get.