Lots of people have given you very specific advice about what frameworks to use, how to approach the problem, etc...
Take it all with a grain of salt. What I'd suggest to get started is create a public github project for it, put together some wireframes and sequence diagrams (publish them in the github project) so that people can see what it's meant to look like and how it's mean to work. Then just start coding.
Post the github project here on HN and ask for contributors. Keep a curated list of features, tasks and bugs in the github project and let people pick them up and help you build it.
Rule #1 though, don't let people get you down. Everyone has an opinion and we software people can be pretty harsh, especially when, frankly, we're just arguing our opinion rather than fact.
Rule #2, done is better than perfect. What's your Minimum Viable Product? Build that, maintain tunnel vision on completing that, then worry about everything else it could do.
Take it all with a grain of salt. What I'd suggest to get started is create a public github project for it, put together some wireframes and sequence diagrams (publish them in the github project) so that people can see what it's meant to look like and how it's mean to work. Then just start coding.
Post the github project here on HN and ask for contributors. Keep a curated list of features, tasks and bugs in the github project and let people pick them up and help you build it.
Rule #1 though, don't let people get you down. Everyone has an opinion and we software people can be pretty harsh, especially when, frankly, we're just arguing our opinion rather than fact.
Rule #2, done is better than perfect. What's your Minimum Viable Product? Build that, maintain tunnel vision on completing that, then worry about everything else it could do.