There are several different ways that OBA can be deployed and used for a transit agency or a group of transit agencies in a given region. I'll give you four examples, but this isn't an exhaustive list:

1. The Puget Sound region, where a regional transit authority, Sound Transit, currently maintains their own OBA servers on behalf of a dozen individual transit agencies. Sound Transit piggybacks on our official OBA apps which you can find in the Play and App Stores. The official apps also work in 10 other cities across the US. This is the ideal for us—and transit riders, imho, and similar to what you see with apps like Citymapper or Transit.

2. New York City, where MTA runs their own OBA servers that power their own branded app and realtime signage throughout the five boroughs.

3. UC San Diego, where the university is using OBACloud to power real time transit information systems for students on campus.

4. Republic of Cyprus and Malaysia (yes the entire countries), where enterprising individual developers have set up their own OBA servers to power realtime transit information systems for their fellow citizens.

The underlying OBA server provides a rich set of REST APIs that make it much easier to build a public transit app than using raw GTFS and GTFS-RT data: https://developer.onebusaway.org/api/where/methods

We also have SDKs for many major languages so that agencies and independent developers can build their own apps on top of OBA servers without having to fiddle around with the intricacies of our APIs. https://developer.onebusaway.org/api/sdk

~~~

Integration with Google Maps is important, and a "yes and" solution. I think there's a lot of value in having public transit-focused apps, especially ones that don't have advertising or questionable privacy issues.

~~~

edit: I noticed you're in Argentina. The Ministry of Transportation maintains its own white label version of OBA called Cuando Subo. https://www.argentina.gob.ar/sube/cuandosubo