Highway☆ now available in the iOS App Store! Next steps...

[catsynth]

New Version 1.1 in progress, with background highway-detection support!

I just sent out a preview to beta-testers.

[catsynth]

Hi all!
I have *finally* had some time to get back to updates (pesky day job has been getting in the way).
a)  A new iOS version will be submitted this week, with iOS 11 compatibility and other fixes.
b)  I have deployed a new admin tool that will help me more efficiently respond to missing/missed highway requests.  I have already started the processing of updating the database and crediting folks for missed routes.

Meanwhile, I have received and read bug reports and will be incorporating them into the next major releases for both platforms.  Hoping to get started on the no-connectivity support, too.

As always, please let me know your thoughts, suggestions, concerns, etc.

Thanks!
-Amanda

[hbelkins]

I recently had to delete and reinstall the app on a couple of devices. When I tried to log in on the reinstalled versions using my Facebook credentials, it kept defaulting back to the login page. The problem seemingly resolved itself the next day, however.

[catsynth]

I recently had to delete and reinstall the app on a couple of devices. When I tried to log in on the reinstalled versions using my Facebook credentials, it kept defaulting back to the login page. The problem seemingly resolved itself the next day, however.

Was that by any chance last Thursday/Friday?  The servers behind the app had a serious issue that fortunately, I was able to resolve.

[hbelkins]

I recently had to delete and reinstall the app on a couple of devices. When I tried to log in on the reinstalled versions using my Facebook credentials, it kept defaulting back to the login page. The problem seemingly resolved itself the next day, however.

Was that by any chance last Thursday/Friday?  The servers behind the app had a serious issue that fortunately, I was able to resolve.

Friday.

[catsynth]

I recently had to delete and reinstall the app on a couple of devices. When I tried to log in on the reinstalled versions using my Facebook credentials, it kept defaulting back to the login page. The problem seemingly resolved itself the next day, however.

Yep, then definitely the server issue.  Fixed Friday night.

Was that by any chance last Thursday/Friday?  The servers behind the app had a serious issue that fortunately, I was able to resolve.

Friday.

[catsynth]

1.1.1 is now available in the Apple App Store!  Please update, especially if you have upgraded your device to iOS 11. (link is in my signature)
I am also caught up on missing-road reports that I had in my queue.  Obviously, that will be an ongoing task...

[bulldog1979]

1.1.1 is now available in the Apple App Store!  Please update, especially if you have upgraded your device to iOS 11. (link is in my signature)
I am also caught up on missing-road reports that I had in my queue.  Obviously, that will be an ongoing task...

I still need credit for M-64, M-67, M-203, US 2 in WI, US 141 in WI, WIS 70, and WIS 101 yet.

[MCRoads]

I got it! So, the onltcomplaint I have is the live camera is a little jerky...

[hbelkins]

If I could make a suggestion...

The app seems to be a data hog. I'm not sure how that could be remedied, but I'd think an option to view map only and not satellite view would help in that regard.

[catsynth]

If I could make a suggestion...

The app seems to be a data hog. I'm not sure how that could be remedied, but I'd think an option to view map only and not satellite view would help in that regard.

Yes, turning off Satellite will be added to the next feature release.  That should reduce the data load quite a bit.

The app does send/receive route data frequently, depending on how fast one is moving, but the data sizes should be relatively small.  There may be ways to optimize that as part of the new feature queuing up requests during poor connectivity, but not yet sure. 

[catsynth]

Hi all.  I've been crazy busy with several projects in the last quarter of 2017, but I'm ready and excited to get back to the Highway☆ app!
It's been great to see people using it in the meantime, and watch myself sink in the leaderboard compared to others

On deck for both iOS and Android:
1) Offline/poor connectivity mode
2) Turn satellite/3D on and off on main view

Longer term:
3) Travel mapping

No specific time frames, but I'm hoping to get some things at least testing in January.
Thanks for your patience.

[catsynth]

And here are some screenshots of the new iOS version!  It should be ready for beta testing this coming week.  If anyone wants to join in the next beta, please PM me.





Android version is already in progress as well, probably about a week behind iOS.

[catsynth]

New iOS version is now available in the App Store.
https://itunes.apple.com/us/app/highway-star/id1209913631?mt=8

[catsynth]

Android beta of 1.2.0 is out tonight.

[mapcat]

I've been playing with the app now for about a week and like it. Catsynth posted in the TravelMapping forum (where I learned about it) seeking ways to incorporate TM data to enhance Highway☆, and suggested that this was the place for discussion.

It's not completely clear to me how TM data would/could be incorporated into this app, since its purpose seems to be different. H☆ users earn points for "encountering" different highways, not for travelling specific lengths of them; TM users record miles of travel on highways, which are considered "clinched" when a user has travelled all segments. Segments in TM exist between intersections with other highways, towns, and random points selected to make the files approximate the shape of the real-world road. Nothing in H☆ corresponds to those segments, which suggests that the framework for H☆'s route files would have to be completely redone. Also, H☆ gives users bonus credit for encountering a highway in additional counties (in the US), and there's no consideration given for county lines in TM.

As a TM user and now a Highway☆ user, I see a benefit to using both methods of tracking my travel, since they are different and serve different purposes. Since both provide rankings for users, and since this thread shows that Catsynth has already generously offered to manually add routes to users' files, it's conceivable that someone who's tracked travel on TM might wish to get credit for routes travelled prior to the development of H☆, which seems it would invite abuse. So I'd personally prefer to keep TM and H☆ separate.

[catsynth]

Thank you for the thoughtful post, and sorry for my delay in replying (busy week).
I do definitely see differences between TM and H☆ in a lot of respects.  But I do see some utility in extending the mission of H☆ to at least allow the creation of travel maps.  On the H☆ side, one of the challenges is keeping it fun and engaging without always having to travel farther from home - I am thinking the ability to record and share trips is one way to do that.  Another is clinching, but as pointed out, that is a much more difficult task.   I'm up for doing architectural changes to the H☆ backend that would facilitate recording trips, although it does appear the goals or not completely the same as TM.

The point about people potentially abusing the system is a serious concern.  At this point, I would not foresee people being allowed to bring past trips from TM or other sources into Highway☆

Open to more thoughts from both communities

[catsynth]

Hi all.  Just wanted to let you all know that I have broken ground on the next major release, which will include trip recording!

Basically, it's just a recording of the path of travel plus highways encountered along the way.  It would be nice to filter it to ones actually traveled upon, if possible, but that is complicated.

Since this project is in the very early stages, there are both a lot of open questions, as well as opportunity for input from the community, so please do share your questions and ideas

Thanks!

- CatSynth (Amanda)

[catsynth]

The iOS version of trip recording is now in early beta.  If you are not in the beta program and would like to try it out, please message me.

There is still an open question of how to score trips, or whether to do so at all.  Thoughts on this particular point are welcome.

Thanks!

[JJBers]

The iOS version of trip recording is now in early beta.  If you are not in the beta program and would like to try it out, please message me.

There is still an open question of how to score trips, or whether to do so at all.  Thoughts on this particular point are welcome.

Thanks!

One point every mile? I'm not sure.
It also seems to not record highways after a while too. Not sure if it's a problem with Android 8.1 not sending out location data, or a app issue.

[Bickendan]

Did a quick jaunt into Vancouver a couple nights ago, up I-5 and back down I-205.
App missed US 30 Bypass (both times), OR 120 (this is ok, it's completely unsigned), and WA 501.

I also randomly got credit for OR 8 well before going to the Portland west metro, and the app doesn't pic up OR 224 or 212 when on I-205.

I also note a lack of singing OR 99W from I-405 or I-5 north of downtown,  but given the ambiguity of 99W north of Tigard, I'm not concerned about it and won't be until ODOT advises me what to do for the Travel Mapping entry.

[catsynth]

Thanks for the idea re: trip scoring.
If it's Android, was the app in the background when it stopped recording?  I just got some reports of background service crashes.

The iOS version of trip recording is now in early beta.  If you are not in the beta program and would like to try it out, please message me.

There is still an open question of how to score trips, or whether to do so at all.  Thoughts on this particular point are welcome.

Thanks!

One point every mile? I'm not sure.
It also seems to not record highways after a while too. Not sure if it's a problem with Android 8.1 not sending out location data, or a app issue.

[catsynth]

Thanks for the reports.  I was actually in PDX a couple of months ago and had fun with the app myself there
OR 212 is definitely in the app, but I have observed inconsistency at freeway junctions so that may be it.

I will try and investigate the others as well.

Did a quick jaunt into Vancouver a couple nights ago, up I-5 and back down I-205.
App missed US 30 Bypass (both times), OR 120 (this is ok, it's completely unsigned), and WA 501.

I also randomly got credit for OR 8 well before going to the Portland west metro, and the app doesn't pic up OR 224 or 212 when on I-205.

I also note a lack of singing OR 99W from I-405 or I-5 north of downtown,  but given the ambiguity of 99W north of Tigard, I'm not concerned about it and won't be until ODOT advises me what to do for the Travel Mapping entry.

[tckma]

Downloading it now.  It would be nice if this interfaced with tm.teresco.org.  Maybe it does.  I have not opened it yet - it's still downloading.

[catsynth]

Downloading it now.  It would be nice if this interfaced with tm.teresco.org.  Maybe it does.  I have not opened it yet - it's still downloading.

Not yet, but that's absolutely on my list.  The trip-recording feature was done with that in mind.