V1 Integration with the ALP

[Vortex]

From what I understand this was researched and it is NOT an issue. Plus they can use the dedicated GPS too if they need to.

Cool. With the remote M3's, if you go for the ALP integration option currently, you get a simpler install and a savings of a few hundred bucks. You give up GPS lockouts, Live compatibility, the external speaker, and the Bel sounds. (I wish we could choose other sounds for ALP radar alerts)

With the V1 integration option, we would save the $50 for the V1C but have to spend another $100 for the R/G module. This could potentially save us the $$ and space in having a dedicated YaV1 phone, if we run everything on our main phone. For iOS users though, the background alerting options are pretty limited and if the app isn't in the foreground (you're playing music, on the phone, etc.) we can't see things like frequency information, arrows if running in dark mode, and so on, so it may make more sense to still go for a dedicated Android display if you're an iOS user, just like we do for YaV1.

Speaking of YaV1, coming up with a reason to replace that is really the main thing for me. Really the app would have to basically copy all of YaV1's features, if not add more features above and beyond what YaV1 currently offers. Both Francky and AL's engineers are good about implementing bug fixes quickly so that's a plus. Francky is currently faster since he doesn't have all the other AL stuff on his plate. Given that the Android platform is better for this app, the main question really seems to be why we'd migrate away from YaV1.

[BestRadarDetectors]

Cool. With the remote M3's, if you go for the ALP integration option currently, you get a simpler install and a savings of a few hundred bucks. You give up GPS lockouts, Live compatibility, the external speaker, and the Bel sounds. (I wish we could choose other sounds for ALP radar alerts)

With the V1 integration option, we would save the $50 for the V1C but have to spend another $100 for the R/G module. This could potentially save us the $$ and space in having a dedicated YaV1 phone, if we run everything on our main phone. For iOS users though, the background alerting options are pretty limited and if the app isn't in the foreground (you're playing music, on the phone, etc.) we can't see things like frequency information, arrows if running in dark mode, and so on, so it may make more sense to still go for a dedicated Android display if you're an iOS user, just like we do for YaV1.

Speaking of YaV1, coming up with a reason to replace that is really the main thing for me. Really the app would have to basically copy all of YaV1's features, if not add more features above and beyond what YaV1 currently offers. Both Francky and AL's engineers are good about implementing bug fixes quickly so that's a plus. Francky is currently faster since he doesn't have all the other AL stuff on his plate. Given that the Android platform is better for this app, the main question really seems to be why we'd migrate away from YaV1.

You guys need to also stop thinking like enthusiasts.... I know its hard but you guys are maybe 1% of the market. You need to think like everyday users which is the majority of our customers. When thinking of new integrations we have to clear our mind and think of selling easy integrations that everyday users can use and operate without cluttering the support lines. YaV1 is not for the everyday user and is very complicated to most non enthusiasts. The AL Integration will be much easier to learn and use and for an average person using a new V1 the integration should be very exciting for them because their V1 does not have voice alerts and does not have any frequency display without V1C.

We might do it is phases but it will be a polished product when released.

[Vortex]

You guys need to also stop thinking like enthusiasts.... I know its hard but you guys are maybe 1% of the market. You need to think like everyday users which is the majority of our customers. When thinking of new integrations we have to clear our mind and think of selling easy integrations that everyday users can use and operate without cluttering the support lines. YaV1 is not for the everyday user and is very complicated to most non enthusiasts. The AL Integration will be much easier to learn and use and for an average person using a new V1 the integration should be very exciting for them because their V1 does not have voice alerts and does not have any frequency display without V1C.

We might do it is phases but it will be a polished product when released.

lol, fair enough. Having an easier to use and learn app would be a benefit compared to YaV1. Coming into it with more of a beginner's mind, having a frequency display and voice alerts is a big upgrade. We've gotten a bit used to it now that the V1C has been out a while, but I remember how fantastic that was not needing to run another RD like a RL or Plus to get frequency info. That said, given that you're talking to enthusiasts, it still has to offer us something that we'd want above and beyond YaV1 if you'd want us to switch too. For the general population it is a different story, that's true.

One quick thought, it'd be awesome to get Bel radar alert sounds when running an M3 head (or Escort sounds, though they're not as good IMHO) or V1 sounds when running a V1. The V1 has its own sounds built-in (unlike a remote M3 head) and so it's not as important to have audio alerts coming from the app if we can do it from the RD.