Evaluating the app...

Comments

5 comments

  • Official comment
    Beeline Team

    Hey Stuart, thanks for the thorough thoughts - really appreciated. Beeline has always been the culmination of great feedback and user testing, so we'll put this in the pot too. Nic's right - the simulator screen in the app really is a dummy for the real thing - the device has much more sophisticated logic and functionality, so let's see how you get on!

    Cheers,
    Sam

    Comment actions Permalink
  • Nic DAffnay

    I was said that the app is only 'dummy' version as an appetizer for the real thing when connected to an actual Beeline device.  

    0
    Comment actions Permalink
  • Stuart Fisher

    I've got one now. I'm really impressed so far BUT I've only been using it for cycling around town, which, for the most part, I don't really need to do as I know where I'm going. However, I'm planning to do some "100km rides into the unknown" soon, so it has helped me get used to it.

     

    First off, I can confirm that reverse route in compass mode is broken (on Android 7.0, with build 2.5.2056). My route to work is about 22km and I've put in about 12-15 waypoints. When I reverse the route, the end point moves somewhere close to the start point and I get another line from the old end point to the new end point. This just seems really weird to me and it's a pain to have to manually re-create the route in the opposite direction. Please fix this.

     

    Second, I figured out how to insert waypoints. Tapping on the line between two waypoints puts a new one in. That's really good now that I know how to do it!

     

    Third, I'm still a bit perplexed by some of the ways in which route saving is handled. You are allowed to have routes with the same name, which is unlike any other file system I've ever come across. I'm also confused as to why you'd want to capitalise the first letter in every word when entering a name for the route. Again, I've never seen this done before.

     

    Fourth, I didn't go directly home from work today as I was going somewhere else first. I wondered what would happen if I brought up the route to home. I was really impressed with the way the app just drew a line from where I was to the first waypoint on the route and then allowed me to step through the waypoints to choose one to get me back on the route home. Brilliant! Kudos to the developers that added that feature!

     

    Fifth, I have a couple of feature requests. 1. I was thinking that quite often on bike rides I will discover something interesting (from the mundane, such as finding a supermarket that I didn't know was there, to something more spectacular, like beautiful views from the top of a hill). I'd love to have the ability, with just a couple of button presses, to drop a pin. Later when I review the ride on the phone, I could add a comment to the pins I'd dropped to record what I'd found. 2. My old Garmin has the ability to count laps when you return to the start location. It would be great if you could make a route that had the start and finish at the same point and set the number of laps you want to do. I've got a cycle ride coming up that is going to be 48 laps, so I could do with having this feature. What I think I'll try and do is make a gpx file for it. I think that should work, but I imagine I won't be able to get any visual indication of how many laps I've done during the ride.

     

    I'll let you have some more feedback after I've done a few of those 100km rides!

    Stuart

     

     

    0
    Comment actions Permalink
  • Stuart Fisher

    I've tried route mode now. I was only going to go 60km but the Beeline got me there with so little trouble that I continued on, which made the ride over 100km. I then cycled all the way back without ever having to look at the map at all. Google does an amazing job with routes but it does get things a bit wrong ocassionally, which is another reason why being able to drop pins would be useful. The nice thing about the Beeline though is that when you do go wrong it's very obvious, and its very easy to figure out what you've done wrong and get back on track.

     

    One final thought, I noticed that the next turn indicator often makes it impossible to read the progress display. Is there a reason why you didn't put the progress bars at the bottom instead? There's empty space there and it would mean that you have the two directional indicators at the top and the two distance indicators at the bottom. Was this something that you considered? I'm a developer and sometimes with my own projects I manage to overlook the most obvious things, only realising much later that I should have done it differently. Perhaps you have just overlooked this possibility!?

    BTW, I gave you a 5 star review on Wiggle too. Thank you for making this fantastic new invention!

     

    0
    Comment actions Permalink
  • Stuart Fisher

    A bit more feedback... It's crashed on me a couple of times now. The screen just freezes and maybe 10-15 minutes later it goes back to the off screen and you can enter your route again. Both times this happened I was due to stop and have a break, so it wasn't a big deal. Also in both cases the small spinning  icon was visible, so maybe there was some issue with the synchronising.

     

    I like having a screen that shows you the total time and distance travelled but it would be nice if you could also have the distance remaining too. I appreciate there isn't enough room (and adding more screens would mean more button presses), but perhaps you could display both distances by showing each one for a few seconds and then changing to the other one. If you put an up arrow next to the distance travelled and a down arrow next to the distance remaining that would work.

    0
    Comment actions Permalink

Please sign in to leave a comment.