Cities should just pay reasonable salaries to a couple developers and build apps themselves. "Each team returns to Bay Area headquarters and then has seven mon

Cities should just pay reasonable salaries to a couple developers and build apps themselves. "Each team returns to Bay Area headquarters and then has seven months to develop their application for their city." Nevermind the potential issues from giving development seven months without having heard requirements. My question is, why just one application? Cities are huge machines. I have enough trouble navigating around a single councilwoman's website - let alone the DMV's. How is one application supposed to service an entire city in a meaningful way? Before reading the details of this program, I imagined it would be something like this: CFA puts you up in the city you'll be helping. Lodging, food, transportation, etc. Instead of visiting the city you're helping, you visit SF headquarters - for a couple weeks, to go over your vision for development. After identifying the applications that would be most beneficial to the city's residents, you build them. The applications start small – you iterate as you get feedback from citizens. The benefit of this approach over CFA's is that you don't end up with one monolithic application that is difficult to add functionality to. Instead, you have a few examples of efficiency throughout the city. Enough examples, hopefully, that other departments will be inspired to invest in their own department's application.