Astro vs React vs Flutter vs TBD

[DanHugoDanHugo]

There are two schools of thought when it comes to wireframes and demos and whatnot:

• Spend the time and then throw it away and build the "real thing." Basically an MVP of fluff.
• Develop a real alpha release (0.1.0 alpha, or something) and show that as a demo, throwing away none.

The backend is not quite as big a deal (famous last words), let's assume we have a RESTful and maybe GraphQL-able API endpoint to work with, that we control, which provides static and real time data as the current API does (visit https://www.rtcsnv.com/ways-to-travel/transit-services/for-developers/ for that data and some other info, it's a start for us and is the working data for transit today), and then any augmentation. This way we can develop around existing data access and add value with some augmentation.

So then it comes down to how to build that alpha to work with and discuss, so that it will work on a mobile device in the field, and on a regular old web browser. This makes Astro, React, and Flutter Web all reasonable ideas, which is most reasonable? Is it the TBD option?

I think a nice v0pre-alpha would be a web page with a pane that pulls real time data from the rtcsnv real time data source. Once that works, we try the same on an Open Transit (cfv) data source, and along the way we should be able to switch back and forth… this means the back end and front end will always be able to test each other, which will come in handy.

Some additional features are mentioned in the overview, and there are almost certainly even more than that, not to mention what actual riders and rtc ops people and whomever else, mention over time.