- team size 2-3 people - someone with a "vision" who decides what to build, and someone who keeps track of what to do next. (Can be the same person) - mostly

- team size 2-3 people - someone with a "vision" who decides what to build, and someone who keeps track of what to do next. (Can be the same person) - mostly depends on how complicated the UI is. If you need to do a couple of revisions, a feature will easily take 6 months. Minor features take two or three weeks. Some features we talk about for years before we implement them. - automatic tests and a lots of beta testers - Github issues, commit messages, code comments, and lots of video calls - we write automatic tests for most of the business logic, and do manual tests for UI things. And we make it easy for beta testers to contact us, because stuff always slips through. - we try to stick to platform best practices, so a lot of decisions come down to "what's the most natural way to solve the problem in this framework". Lots of whiteboarding, diagrams, and design documents are created when starting with a new feature. We don't follow a specific method. - Start with the bare minimum and make sure you get people to use it as soon as possible. Watch people use your software -- what you find intuitive might not be intuitive for your users. Users will send feedback only when they want something. Don't build everything people ask for, make sure it's actually a good fit for the app first.