Highway Radar v2.1 beta

[ferius]

Just a quick note that I've released v2.1.2 to public, so no need to be a beta tester to use it anymore. v2.1.2 has the same features as v2.1 but adds some bug fixes found during beta testing.

 

[Euurx]

Will this be available for iPhone users?

 

[ferius]

Will this be available for iPhone users?

Hi @Euurx, I've summarized my thoughts about an iOS version in https://www.rdforum.org/index.php?threads/96516/

 

[Euurx]

Hi @Euurx, I've summarized my thoughts about an iOS version in https://www.rdforum.org/index.php?threads/96516/

I guess that gives me the all more reason to change the android Didn't know that you had to buy $1500+ of Apple Dev equipment. For some reason I thought you could do it without it

 

[UnderCover]

iOS users... Simple fix... Switch to Android!
Advantage, it's very tweakable and you can arrange apps and hide apps plus.. have Highway Radar and lots more!
I do know that iPhone speakers are very loud and a good benefit for the user.

 

[G37X Jockey]

Just a quick note that I've released v2.1.2 to public, so no need to be a beta tester to use it anymore. v2.1.2 has the same features as v2.1 but adds some bug fixes found during beta testing.

Ferius, I've been looking for this update version but nothing is showing up in my updates listing on Playstore. Do I have to leave the beta program to see it?

 

[TurboDriver]

Ferius, I've been looking for this update version but nothing is showing up in my updates listing on Playstore. Do I have to leave the beta program to see it?

I don't see it either and I am not beta.

 

[lugnuts]

I don't see it either and I am not beta.

im not seeing it either

 

[ferius]

Ferius, I've been looking for this update version but nothing is showing up in my updates listing on Playstore. Do I have to leave the beta program to see it?

I don't see it either and I am not beta.

im not seeing it either

Oops! I just realized that I've prepared the release but forgot to press the "Start roll-out" button (the last step of publishing new version). Thanks for pointing out, the app should be on your devices soon.

 

[Jesse]

Oops! I just realized that I've prepared the release but forgot to press the "Start roll-out" button (the last step of publishing new version). Thanks for pointing out, the app should be on your devices soon.

Update came through here. Really appreciate the app!

 

[G37X Jockey]

The camera alert bug is fixed now. Great work Ferius.
I driving in LA and am amazed how many helicopters the LAPD have.

 

[ferius]

The camera alert bug is fixed now. Great work Ferius.
I driving in LA and am amazed how many helicopters the LAPD have.

I actually teleport my emulator to LA whenever I need to test aircraft alerts, there is always something flying there.

 

[aim4squirrels]

Oops! I just realized that I've prepared the release but forgot to press the "Start roll-out" button (the last step of publishing new version). Thanks for pointing out, the app should be on your devices soon.

So, I know you're trying to avoid any "Imperial entanglements" with certain other borrowed reporting systems... Have you ever thought about taking it off the store completely and just making it a third party app hosted on a personal website, so that people have to actively look for it to run into it, and invest the time to figure out how to make their carrier based phones accept 3rd party apps? This might help you avoid unwanted attention from the overlords at G.

It's just a thought...

 

[ferius]

So, I know you're trying to avoid any "Imperial entanglements" with certain other borrowed reporting systems... Have you ever thought about taking it off the store completely and just making it a third party app hosted on a personal website, so that people have to actively look for it to run into it, and invest the time to figure out how to make their carrier based phones accept 3rd party apps? This might help you avoid unwanted attention from the overlords at G.

It's just a thought...

Hi, I did think about it. However, this will make distribution harder for me as well (no background auto-updates possible, have to setup own crash reporting, etc), I'm not sure I want to go with that now. Moreover, the imperia can even block applications outside of their Store on their devices.

If I find a way to borrow the information from the "certain other reporting system", I'll probably still go with an app in the store, but lacking crowdsourced alerts and supporting separately distributable plugins from "third-party developers", probably via RDF enabling integration with reporting systems. However, for now, I haven't reversed the "certain other reporting system" protocol yet (they use something proprietary not very easy to understand), so I don't see any need of splitting the app -- request for the hostname works just fine.

 

[aim4squirrels]

Hi, I did think about it. However, this will make distribution harder for me as well (no background auto-updates possible, have to setup own crash reporting, etc), I'm not sure I want to go with that now. Moreover, the imperia can even block applications outside of their Store on their devices.

If I find a way to borrow the information from the "certain other reporting system", I'll probably still go with an app in the store, but lacking crowdsourced alerts and supporting separately distributable plugins from "third-party developers", probably via RDF enabling integration with reporting systems. However, for now, I haven't reversed the "certain other reporting system" protocol yet (they use something proprietary not very easy to understand), so I don't see any need of splitting the app -- request for the hostname works just fine.

I completely understand the crash reporting feature and it's usefulness in the development and beta testing phase. That's very useful to you as you develop the app and add new functionalities.

The auto updates feature is nice, but not 100% necessary from a die hard user standpoint. If you were to post on RDF that you had a new version available, the die hard users here would likely go out of their way to download your latest version.

It's true the Google can "nuke" you remotely even if you aren't on the app store, but if you're not on Their app store in the first place, they'd likely need to be tipped off about your existence to nuke you. It seems like they have enough problems controlling their own store, much less looking for outside problems.

I just read an article yesterday that they are finally trying to crack down on apps that ask for background location service requests without actually needing that data for the app's functionality. They are going to do an audit of all apps requesting background location permissions to see if the apps requests are warranted: https://www.google.com/amp/s/www.zd...ps-accessing-location-data-in-the-background/

You are the developer of a fantastic app, and I truly appreciate what you have accomplished and that you were willing to share it with the community. I'm just trying with all my might to help make sure you don't get shut down, and lose this invaluable resource.

 

[ferius]

I completely understand the crash reporting feature and it's usefulness in the development and beta testing phase. That's very useful to you as you develop the app and add new functionalities.

The auto updates feature is nice, but not 100% necessary from a die hard user standpoint. If you were to post on RDF that you had a new version available, the die hard users here would likely go out of their way to download your latest version.

• If there is no auto-update, then users (except for maybe a couple percent) will just stop updating the application -- that is how it actually works.
• If there is an update notification, then still the majority would still dismiss it because "it works and already satisfies me".
• Even auto-download and a request to click one button when starting the app will be dismissed very often because people start the app when they are just about to start driving and don't want to wait.
• And if I block the app features if the update isn't installed then people will be very pissed when they are in a hurry and the app just refuses to work.

All of these options are much worse than a silent auto-update working via Play Store.

It's true the Google can "nuke" you remotely even if you aren't on the app store, but if you're not on Their app store in the first place, they'd likely need to be tipped off about your existence to nuke you. It seems like they have enough problems controlling their own store, much less looking for outside problems.

That does make sense, I can't argue with that.

I just read an article yesterday that they are finally trying to crack down on apps that ask for background location service requests without actually needing that data for the app's functionality. They are going to do an audit of all apps requesting background location permissions to see if the apps requests are warranted: https://www.google.com/amp/s/www.zd...ps-accessing-location-data-in-the-background/

Just read the article and it looks like Highway Radar uses background location in the absolutely legit way -- it doesn't do it secretly (notification is always present) and there is a good reason for background location capability (working in the background).

You are the developer of a fantastic app, and I truly appreciate what you have accomplished and that you were willing to share it with the community. I'm just trying with all my might to help make sure you don't get shut down, and lose this invaluable resource.

Thanks for the kind words. For now, considering I have pretty limited resources for development, I want to focus on the app features, but not on preventing a problem that hasn't happened yet and there is no guarantee it will happen at all. If anything goes wrong, switching to self-distribution wouldn't be a problem at all, even after "nuking" the app.