12 riders ran 245 sessions in 53 journeys on: 6/8/24 6/15/24 6/22/24 6/29/24 7/6/24
bikeID: 1
Comments: disconnect
Phone: NA . Browser: unknown
bikeID: 2
Comments:
Phone: NA . Browser: unknown
bikeID: 3
Comments: disconnect
Phone: NA . Browser: unknown
bikeID: 4
Comments:
Phone: NA . Browser: unknown
bikeID: 5
Comments:
Phone: NA . Browser: unknown
bikeID: 6
Comments:
Phone: NA . Browser: unknown
bikeID: 7
Comments:
Phone: NA . Browser: unknown
bikeID: 8
Comments: not connected
Phone: NA . Browser: unknown
bikeID: 9
Comments:
Phone: NA . Browser: unknown
bikeID: 10
Comments: did not appear on screen, had to recconect
Phone: NA . Browser: unknown
bikeID: 10
Comments:
Phone: NA . Browser: unknown
bikeID: 11
Comments: not connected
Phone: NA . Browser: unknown bikeID: 1
Comments: I activate the sound in the middle of the ride. No sound for flocking and slower modes
Phone: NA . Browser: Safari
bikeID: 2
Comments: issues connecting. was able to allow Safari to see location, byt not the website. website promt to the location never popped up.
Phone: NA . Browser: Safari
bikeID: 3
Comments: Went well for the most parti, first persson POV view awas skewed a bit so I could not see the attractor
Phone: NA . Browser: Chrome
bikeID: 4
Comments: Slower/Faster Instructions were slightly lapping compared to the actual speed. Missng in dataset. assigned to 03b4d
Phone: NA . Browser: Chrome
bikeID: 5
Comments: speed sounds were not consistent. "slower" (pink) and "flocking" blue sounds did'nt come through
Phone: NA . Browser: Safari
bikeID: 6
Comments: I only had sound for "faster". Missing in dataset
Phone: NA . Browser: Chrome
bikeID: 7
Comments: Didn't have sound
Phone: NA . Browser: Safari
bikeID: 8
Comments: NA
Phone: NA . Browser: Safari
bikeID: 9
Comments: All good!
Phone: NA . Browser: Chrome
bikeID: 11
Comments: No sound
Phone: NA . Browser: Safari bikeID: 3
Comments: No ride sound on "faster byt not for "flocking" or "slower
Phone: NA . Browser: Chrome
bikeID: 4
Comments: No signal session.
Phone: NA . Browser: Chrome
bikeID: 7
Comments: The adaptation view is working better than last time
Phone: NA . Browser: Chrome
bikeID: 9
Comments: No ques provided
Phone: NA . Browser: Chrome bikeID: 1
Comments: It mostly showed me the faster mode
Phone: NA . Browser: Chrome
bikeID: 2
Comments: only audio for faster prompt. no audio for "flocking". Speed was good. "attractor trackor" could be called the "attractor"
Phone: NA . Browser: Chrome
bikeID: 3
Comments: Worked fine
Phone: NA . Browser: Chrome
bikeID: 4
Comments: Good. Speed was okay.
Phone: NA . Browser: Chrome
bikeID: 5
Comments: No issues. I have better inteation with the sound than the visuals. it's interesing to this in groups since we hall have different reaction threstholds but still somehow syncronize to the stimuli
Phone: NA . Browser: Safari
bikeID: 6
Comments: I had sound on for "faster and "slower" but not for flocking. I would be more comfortable going faster
Phone: NA . Browser: Chrome
bikeID: 7
Comments: Sound only to go faster
Phone: NA . Browser: Safari
bikeID: 8
Comments: everything was fine
Phone: NA . Browser: Safari
bikeID: 9
Comments: Unexpected behaviour towards end of journey: Speed fluctuated a lot. Wend from green to red to green to nblue. Speed was fine
Phone: NA . Browser: Chrome bikeID: 1
Comments: The flocking mode didn't have sound. I could identify my group
Phone: NA . Browser: Safari
bikeID: 3
Comments: worked fine. couldn't tell the difference between the two groups until the 2nd half of the route.
Phone: NA . Browser: Chrome
bikeID: 5
Comments: The one inconvenience I noticed this time that it gets difficult to cruise when a group with different speeeds. When we one not used to ride in groups, there may be higher potential for incidents happening.
Phone: NA . Browser: Safari
bikeID: 7
Comments: Sound only to go faster. Hard to keep up with the speed when the path isn't wide enough and there's too many people
Phone: NA . Browser: Safari
bikeID: 9
Comments: All good. It was hard to confugure the map direction as I could not see green dot.
Phone: NA . Browser: Chrome bikeID: 2
Comments: No audio for flocking or slower for flocking i don't know what to do so I just try to match the ghost, but often forget if the gohst is red or green
Phone: NA . Browser: Chrome
bikeID: 4
Comments: Good. Needed to reccomnect for session ID to appear
Phone: NA . Browser: Chrome
bikeID: 6
Comments: I waas able to identify my group. The attractor's speed fluctuated a lot throughout the route
Phone: NA . Browser: Chrome
bikeID: 8
Comments: My group had trouble staying as a flock
Phone: NA . Browser: Safari bikeID: 1
Comments: My phone fell to the ground in the first segment, so I have to stop and get it. I try to follow the attractor as fast as I could, but I could not reach the group
Phone: NA . Browser: Safari
bikeID: 4
Comments: Good. Speed was okay. (may be a bit fast in certain parts)
Phone: NA . Browser: Chrome
bikeID: 6
Comments: I like the speed of this attractor. It was faster and more constant than the other time
Phone: NA . Browser: Chrome
bikeID: 8
Comments: Everything was fine
Phone: NA . Browser: Safari bikeID: 2
Comments: pace was still a bit slow. still no flocking or slower audio
Phone: NA . Browser: Chrome
bikeID: 3
Comments: Worked fine
Phone: NA . Browser: Chrome
bikeID: 5
Comments: No technical issues. Everything worked fine as predicted and expected. I found it better to stay on the back of the group, it made it more enjoyable
Phone: NA . Browser: Safari
bikeID: 7
Comments: only sound to go faster
Phone: NA . Browser: Safari
bikeID: 9
Comments: All good. Figured out functionality
Phone: NA . Browser: Chrome
bikeID: 12
Comments: ProgrMorning said I should go faster (green signals, except for the first few feet, when it said I should go slower
Phone: NA . Browser: Safari bikeID: 2
Comments: Sometime the sounds dont work. I think also that the screen colors fulls; Because I compared it with my classmate.
Phone: NA . Browser: Safari
bikeID: 4
Comments: Might want to add voice to tell the person to speed up or slow down. Flocking sound worked for me. I used Chrome, might not work for Safari
Phone: NA . Browser: Chrome bikeID: 1
Comments: The red and green made sound bot but didnt. I like more that the blue doesnt sound because yout realize that you are good with the sound. Assigned to cq0ay
Phone: NA . Browser: Safari
bikeID: 7
Comments: Maybe it would be better one kind of some for you bike in flocking, if your biking from the tracker, the frequency, the frequency of some should increase. If you are should ?? It should emit a different sound to decrease speed.
Phone: NA . Browser: google Chrome bikeID: 1
Comments: First Route showing
Phone: iPhone . Browser: Safari
bikeID: 3
Comments: route was shown
Phone: iPhone . Browser: Chrome
bikeID: 4
Comments: Just getting used to the e-bike and the route. Nothing unusual
Phone: Android . Browser: Chrome
bikeID: 7
Comments: None(I wish my hile seat was flutter)
Phone: Android . Browser: Chrome
bikeID: 9
Comments: First Route. Test?
Phone: Android . Browser: NA bikeID: 1
Comments: Using adaptive height made it difficult to see the attractor dot. Felt a little crowded on the smlall bilce paths. Comfortable pace.
Phone: iPhone . Browser: Safari
bikeID: 3
Comments: positives: it gMorningeified bikw riding, making it more fun and excitign. Negatives: Attractor doesn't seem to keep sense and size of pedestrians/ number of rider. you can maybe increease the radius and flocking based on these conditions.
Phone: iPhone . Browser: Chrome
bikeID: 4
Comments: At times, it becMorninge haard to keep up with the flock because of the traffic of other participants. Twoards the end of the loop, wwe passed a large group of pedistrians, some of whom were startled by our speed
Phone: Android . Browser: Chrome
bikeID: 6
Comments: No problems this time, the sound worked better than in previous days. More communication with the participants this time.
Phone: iPhone . Browser: Chrome
bikeID: 7
Comments: The electric assists on the hile is unpredictable. It for rreal interesting when we encountered pedestrians near the end of the rout
Phone: Android . Browser: Chrome
bikeID: 8
Comments: Worked fine, wish map rotation automatically changed to pint towards attractor
Phone: iPhone . Browser: Chrome
bikeID: 9
Comments: Large groups of pedestrians on the sidewalks. Potholes. Bikers dont always uses signal or use bike lanes. obstructions in bike lane
Phone: Android . Browser: NA bikeID: 1
Comments: A little faster. Not used to bike with a motor or without selectable geaers. Top down view was much better .
Phone: iPhone . Browser: Safari
bikeID: 3
Comments: All of the rides had better sense and the route/speeds to follow and was much smoother than the first attempts. Attractor sits speeding kind of arbitraily
Phone: iPhone . Browser: Chrome
bikeID: 3
Comments: Was similar to 01097. But was congested and flocking is easier to do without so many riders
Phone: iPhone . Browser: Chrome
bikeID: 4
Comments: At the beginning of the loop, I was in front and it wanted me to slow down. But very soon after, it wqanted me to speed up. Other than that, it seemed normal
Phone: Android . Browser: Chrome
bikeID: 6
Comments: I'd suggest to pre-load the route with a more visual line (thicker) so you know where yart gounf and where you can
Phone: iPhone . Browser: Chrome
bikeID: 7
Comments: Discoured that i can change geaars! Seems there are tries when you can easily collide with others
Phone: Android . Browser: Chrome
bikeID: 8
Comments: Perfect cruising speed
Phone: iPhone . Browser: Chrome
bikeID: 9
Comments: Obstruction in bike lane. Riding in a close group seems more hazardous. Potholes
Phone: Android . Browser: NA bikeID: 4
Comments: There were a lot of speed changes this time, and sometimes we separated and then rejoined each other. At one point, I saw someone near me go slightly into a strip of gravel while trying to pass someone else
Phone: Android . Browser: Chrome
bikeID: 6
Comments: I had problems with the sound when in "flocking" and "slow". I pressed several time the "play sound button without success.
Phone: iPhone . Browser: Chrome
bikeID: 9
Comments: Obstruction in bike lane. Potholes. Bikes can be unpredictable without signlaing or swerving into bike lane
Phone: Android . Browser: NA bikeID: 1
Comments: Good pace. Easy to stay with attactor. No sound during flaking, only during speed up/slow down cues
Phone: iPhone . Browser: Safari
bikeID: 7
Comments: I Morning not sure if I like the cluster; I think we all have to agree on safe biking rules
Phone: Android . Browser: Chrome
bikeID: 8
Comments: Good ride overall. was wearing cMorningilla and tried to stay in the back of the pack for the first time. after was blocked from being able to go faster safely. Maybe increase flocking zone radius for bigger groups?
Phone: iPhone . Browser: Chrome bikeID: 1
Comments: Nice pace. No sound again during flockin, only during speed up/slow down cues. Seemed interesting that slow down cues would happen much fuster than speed up cues
Phone: iPhone . Browser: Safari
bikeID: 4
Comments: We split up early and stayed that way. I was in a group of 4, which felt better 7- not too crowded. I think the speed fluctuations mentioned in runs #35 were because the attractor takes corners at a different speed from me; that happened a few times on this run. By now, I dont really need the visual interface- the audio is enough
Phone: Android . Browser: Chrome
bikeID: 7
Comments: If bycicling is to become a bigger thing, morre training and basic rider and bikership is needed
Phone: Android . Browser: Chrome
bikeID: 9
Comments: SMorninge comments as above.
Phone: Android . Browser: NA bikeID: 3
Comments: Speed was right where I wantedt it to be. The smaller cluster made it easier to maintain "flocking" and was overall the best of the rides I today felt like a gMorningeified version of the movie "speed"
Phone: iPhone . Browser: Chrome
bikeID: 6
Comments: No problems this time. Another suggestion is to limit the attractor to a certain number of bikers so you can ride without being so crowded.
Phone: iPhone . Browser: Chrome
bikeID: 8
Comments: Great ride, this speed is perfect for me
Phone: iPhone . Browser: Chrome bikeID: 1
Comments: Felt fine. This bike can only go so fast before the pedals don't do anything.
Phone: iPhone . Browser: Safari
bikeID: 3
Comments: We didnt swarm together at all. It was ejust either a row or a line
Phone: iPhone . Browser: Chrome
bikeID: 4
Comments: I was trying to speed up to keep up witht he people ahead of me, but couldnt get my bike to gear up. We definentrly lost contact at times, which isnt ideal for safteu in numbers -although in the previous runs we had bunched togerther too much in my opinion.(E.g) riding 2-3 abreast and weaving at times)
Phone: Android . Browser: Chrome
bikeID: 6
Comments: No problem at all
Phone: iPhone . Browser: Chrome
bikeID: 7
Comments: Fewer chances of collisions!
Phone: Android . Browser: Chrome
bikeID: 9
Comments: Folding bikes 20'' wheels are slower than regular 206'' or 700c
Phone: Android . Browser: NA bikeID: 1
Comments: *Potholes *Sudden Accellerations *Sometimes instructed to go faster but no gearing to do so. End up spinning pedals
Phone: iPhone . Browser: NA
bikeID: 2
Comments: Very neat. It took a little bit to get used to the motor kicking on, but it was good feedback that I needed to push a little harder, or when the pedals didn't do anything I knew I needed to slow down, even though I had audio feedback
Phone: iPhone . Browser: Bluefy
bikeID: 4
Comments: It felt pretty normal. I still couldn't get my bile to stay in gear 3, and I was often towards the back of the group, but nothing special
Phone: Android . Browser: Chrome
bikeID: 6
Comments: When the tracker said faster it would not turn the motor on and when it said slower the motor would turn on for a quick second.
Phone: Android . Browser: Chrome
bikeID: 7
Comments: The tracker was way too fast, it was a little hard to follow the tracker
Phone: Android . Browser: Chrome
bikeID: 8
Comments: Much more controllable and enjoyable with the speed limiter in place. Less distractions (sound of flocking on phone), can basically just keep constant effort and know that Im flocking.
Phone: iPhone . Browser: Bluefy
bikeID: 9
Comments: i liked the sounds changeds for the flocking and slower modes. I felt more connected with the visual/sounds signals. Is hard sometimes ride in group because tou dont have enough speed to accelerate.
Phone: iPhone . Browser: Bluefy bikeID: 1
Comments: Potholes, Sudden Accelerations, More traffic and pedestricans than this Morning. Hard to predict where other bikers will go. Some on/off bike lanes
Phone: iPhone . Browser: NA
bikeID: 2
Comments: Didn't feel it the motoras much this time, even though it told me to fo faster a few more times this round.
Phone: iPhone . Browser: Bluefy
bikeID: 6
Comments: SMorninge issue!! Riding speed was good
Phone: Android . Browser: Chrome
bikeID: 8
Comments: Good ride overall. Definently harder to maintain momentul and pedal w/o assistance harder to maintain momentum and pedal w/o assistant when on the slower attractir's pace. Wanted to be going faster on the straights..
Phone: iPhone . Browser: Bluefy bikeID: 4
Comments: I got stuch at the back of the group early, and only realized I was supposed to be in the ffront forup around the third turn, I did eventually catch up and there were two well defined groups at the end. also, we had to navigate around a few potholes near the beginning.`
Phone: Android . Browser: Chrome
bikeID: 7
Comments: 5.6 miles per hour is too fast. Maybe when the tracker stops in the intersection it should accerlerter slowly.
Phone: Android . Browser: Chrome
bikeID: 9
Comments: We had to go slower in the first segment because a few pedestrians were in the sidewalk. Also there are some roadworks and we hahve to be more careful in the route.
Phone: iPhone . Browser: Bluefy bikeID: 1
Comments: Potholes, Sudden faster/slower switching, sMorninge comments as above
Phone: iPhone . Browser: NA
bikeID: 2
Comments: Felt the motor a lot more this time, even through I was flocking for most of the ride. Lots of fun this loop
Phone: iPhone . Browser: Bluefy
bikeID: 6
Comments: SMorninge iissue!! This time my bike would loose the resistance to slow down during any time
Phone: Android . Browser: Chrome
bikeID: 7
Comments: Maybe it wouldve be grout to have a different sound when the bikes are getting closer to an intersection to speed down.
Phone: Android . Browser: Chrome bikeID: 4
Comments: I still fond that the attractor takes corners and intersections at different speeds from me, and I often take a while to sync back up after the
Phone: Android . Browser: Chrome
bikeID: 8
Comments: Pace was much better on this ride. At times, felt like there wasn't quite eneough space for everybody to be flocking due to the fact that it becMorninge essentially impossible to pass the attractor.
Phone: iPhone . Browser: Bluefy
bikeID: 9
Comments: The flocking sound did'nt work this time. I had to put more effort to get faster.
Phone: iPhone . Browser: Bluefy bikeID: 1
Comments: sMorninge stuff as above, sudden fast/slow prompts, doesnt always slower at intersections, some riders would ride in both bike lanes, no going "faster"
Phone: iPhone . Browser: NA
bikeID: 2
Comments: Not sure if the motor stopped helping or not. I felt like I was able to flock at the correct speed easier than some of the previous rides. I paid a lot more attention to my screen this time.
Phone: iPhone . Browser: Bluefy
bikeID: 4
Comments: This one went smoothly, with only some of the minor comments I made this mornign, like fluctuating directions near corners and stop signs. It wasn't hard to keep up
Phone: Android . Browser: Chrome
bikeID: 6
Comments: With automated speed control I enjoyed my ride a lot more and it was less physically draining
Phone: Android . Browser: Chrome bikeID: 7
Comments: To be honost, low the tracker speed down/up in time. We g... (not sure what the rest says)
Phone: Android . Browser: Chrome
bikeID: 8
Comments: Noticiably harder to stay flocking. Had to pay more attention to the sounds and screen. More people overshot and had to slow down almost to a stop around corners and stop signs. Definetely more dangerous and less organized than with a speeed limiter.
Phone: iPhone . Browser: Bluefy bikeID: 9
Comments: This ride I could be closer more time to the attractor. The flocking sound is not working.
Phone: iPhone . Browser: Bluefy bikeID: 2
Comments: I enjoyed going daster this time. Noticed I still focused on my phone a bit to make sure I was doing close to the speed of the attractor.
Phone: iPhone . Browser: Bluefy
bikeID: 4
Comments: The app told me and one other person to wait quite a while after everyone else left. As a result, I never cought up to the attractor, despite biking as fast as I reasonably could. Im really sweaty now.
Phone: Android . Browser: Chrome
bikeID: 5
Comments: Switched to 5 after 8's battery died. SMorninge as before
Phone: iPhone . Browser: Bluefy
bikeID: 7
Comments: NA
Phone: Android . Browser: Chrome bikeID: 1
Comments: Long wait at the beginning, faster for a whole trip but I manually slowed at intersections and potholes. Out of gears to go any faster. Pedals spinning
Phone: iPhone . Browser: NA
bikeID: 6
Comments: NA
Phone: Android . Browser: Chrome
bikeID: 9
Comments: This time I got more slower signals than usual. In general, it was easy to follow the prompts. The flocking and slower sounds were not working.
Phone: iPhone . Browser: Bluefy bikeID: 1
Comments: stopped by pedestrians, slowed for intersections, slowerd and let others pass as they wasnted to speed ahead, much of the smae comments as last time
Phone: iPhone . Browser: NA
bikeID: 2
Comments: With the bike lanes so narror and so many pople flocking together it felt a little tough to navigate, but it wasn't impossible. Just some more lane needed to be taken while passing and turning.
Phone: iPhone . Browser: Bluefy
bikeID: 4
Comments: I saw someone crash behind me, but the app told me to speed away. I was also a little unsure wheather the cars at the last turn would stop for us. Other than that, it was anormal ryn: pretty smooth, but some awkward speed fluctuations as the attractor ws slow to accelerate after stops and then suddenly caught back up to us.
Phone: Android . Browser: Chrome
bikeID: 5
Comments: Pretty good. Small accident around halfway through, definitely wouldv'e been avoided with speed limits
Phone: iPhone . Browser: Bluefy
bikeID: 6
Comments: The app for rvery run has this error that pops up saying wait for gps signal
Phone: Android . Browser: Chrome
bikeID: 7
Comments: NA
Phone: Android . Browser: Chrome
bikeID: 9
Comments: This ride I had a small accident and at half of the rout I fell from the bikje. My phone was low in battery on the screen. automatically got light off. I was trying to turn it on and I didn't see the bike in front and I hit it, then I fell. Nothing bad, but it made for some of the group get behind.
Phone: iPhone . Browser: Bluefy bikeID: 1
Comments: trial (route training)
Phone: iPhone . Browser: Safari
bikeID: 2
Comments: route training
Phone: iPhone . Browser: Chrome
bikeID: 4
Comments: route training. Started with bike 3 (changed to 4 later since I ran out of battery)
Phone: Android . Browser: Chrome
bikeID: 6
Comments: route training
Phone: iPhone . Browser: Chrome
bikeID: 7
Comments: trial crooter training
Phone: iPhone . Browser: Chrome bikeID: 1
Comments: NA
Phone: iPhone . Browser: Safari
bikeID: 4
Comments: The sounds are intuitive, but GPS signal isnt stable. It changes from fast to slow in a second.
Phone: Android . Browser: Chrome bikeID: 2
Comments: There's lag between speed gps and real speed. All the delays add up, causing innaccuracy. Ghost speed at cross roads/turning sis high. should be lowered.
Phone: iPhone . Browser: Chrome
bikeID: 6
Comments: NA
Phone: iPhone . Browser: Chrome
bikeID: 7
Comments: tend to go faster with app than alone. motivation to be close to the flock, sounds were motivating to ride faster or slower
Phone: iPhone . Browser: Chrome bikeID: 1
Comments: NA
Phone: iPhone . Browser: Safari bikeID: 2
Comments: Delay in speed response. I already slowed down but gps shows im in high speed. Tolerence is too high. eg. my speed is 7.2 m/s and ghost is 6.0 m/s, it is blue/ My speed is 2.2m/s , ghost is 4.0 m/s it is also blue.
Phone: iPhone . Browser: Chrome
bikeID: 4
Comments: GPS has high uncirtainty. someone just stopped (Alomost crashed with #2 bike.) right in front of me due to the visual prompts. Maybe add the sign to the relative distance to ghost?
Phone: Android . Browser: Chrome
bikeID: 6
Comments: orentation gets messy on iPhone 15, directions is scattered and confusing
Phone: iPhone . Browser: Chrome bikeID: 1
Comments: I could follow the attractor better. We were too close. I had to be more careful.
Phone: iPhone . Browser: Safari
bikeID: 2
Comments: Tolerance is too high. My speed 5.0 m/s and ghost is 7 m/s its blue. I need to watch the speeds to match not relying on the color nor sound
Phone: iPhone . Browser: Chrome
bikeID: 4
Comments: I feel this is easier to follow. The ghost kinda wait to long at the stop signs.
Phone: Android . Browser: Chrome
bikeID: 6
Comments: pace was better, but keeping track of my teMorningmaktes was harder, the flock failed
Phone: iPhone . Browser: Chrome
bikeID: 7
Comments: fun! compared to the other one, this one was bettor. almosed crashed once during a street crossing in front of krannert museum
Phone: iPhone . Browser: Chrome bikeID: 1
Comments: I prefer a slower pace. I could hardly keep up.
Phone: iPhone . Browser: Safari
bikeID: 2
Comments: Speed iss innaccurate. Im in 7 m/s and ghost is 5.0 m/s, it asked me to ride faster. It's green. Alsso when start the bike, the electric motor kicks in a little aggressive. when start tationary, the motor shoulf br gentle or not help the rider. The starting force is a little high.
Phone: iPhone . Browser: Chrome
bikeID: 4
Comments: Average speed is faster. and less stopping time at the stop signs. The ghost is accelerating quite rapidly
Phone: Android . Browser: Chrome
bikeID: 6
Comments: near miss and almost hit nearby traffic
Phone: iPhone . Browser: Chrome
bikeID: 7
Comments: the app asked me to go fast all the time was able to go along with their "flock" mode but at the end only
Phone: iPhone . Browser: Chrome bikeID: 7
Comments: too many changes and often even if footor I was not able to reaach the flow state.
Phone: iPhone . Browser: Chrome bikeID: 1
Comments: NA
Phone: iPhone . Browser: Chrome
bikeID: 2
Comments: Sometimes the speed drops drMorningatically. Second, the electric motor on the bike has a delay. It intereferes a half second late when you push the pedal
Phone: iPhone . Browser: Chrome
bikeID: 3
Comments: NA
Phone: iPhone . Browser: Safari
bikeID: 4
Comments: Maybe reduce the stop time at the stop sign?
Phone: NA . Browser: Chrome
bikeID: 5
Comments: everything work better!! The sound concurred with the bike
Phone: iPhone . Browser: Safari
bikeID: 6
Comments: the balance between sound and color is good
Phone: iPhone . Browser: Chrome
bikeID: 7
Comments: Faster than expected. Flocking towards end of journey.
Phone: iPhone . Browser: Chrome
bikeID: 8
Comments: Similar to the previous ride. Only difference is there we have more people now.
Phone: iPhone . Browser: Bluefy
bikeID: 9
Comments: feels nice, I like the speed
Phone: iPhone . Browser: Chrome bikeID: 1
Comments: NA
Phone: iPhone . Browser: Chrome
bikeID: 2
Comments: The electric motor is not linear enough
Phone: iPhone . Browser: Chrome
bikeID: 6
Comments: Almost all the time the app was in red
Phone: iPhone . Browser: Chrome
bikeID: 7
Comments: Faster tin the start and much slower in the end. Was able to keep up much more compared to #1
Phone: iPhone . Browser: Chrome
bikeID: 8
Comments: I was in the slower section. I Morning unable to tell if this was closer thana the first journey but it is possible
Phone: iPhone . Browser: Bluefy bikeID: 3
Comments: NA
Phone: iPhone . Browser: Safari
bikeID: 4
Comments: If using the E-bike, the rider can accelerate faster than the ghost.`
Phone: NA . Browser: Chrome
bikeID: 5
Comments: Just the green made the sound.And I like the top view.
Phone: iPhone . Browser: Safari
bikeID: 9
Comments: Flocking and slower pprompts had no audio
Phone: iPhone . Browser: Chrome bikeID: 1
Comments: NA
Phone: iPhone . Browser: Chrome
bikeID: 3
Comments: It is really helpfull that with the color say the word faster, slower. It helps if you are using sunglasses
Phone: iPhone . Browser: Safari
bikeID: 5
Comments: All colors worked. I like that the blue had a sound that was not to often.
Phone: iPhone . Browser: Safari
bikeID: 7
Comments: Variation of speed is intrested. Skipped from slower to faster which caused some confusion.
Phone: iPhone . Browser: Chrome
bikeID: 9
Comments: Slower prompt felt too slow. Almost was at a stopping point not sure what speed to go during flocking: maintain, slow, or increase speed
Phone: iPhone . Browser: Chrome bikeID: 4
Comments: The prompt changed from slower (~40m) to faster (~60m) in a second
Phone: NA . Browser: Chrome
bikeID: 6
Comments: I lost the sound
Phone: iPhone . Browser: Chrome
bikeID: 8
Comments: this was faster and I felt I have a better understanding of the interface now.
Phone: iPhone . Browser: Bluefy bikeID: 1
Comments: Bike slowed down and would'nt move properly like i disconnected and connected again
Phone: iPhone . Browser: Chrome
bikeID: 2
Comments: bike harder. Disabled motor during movement. Motor still kicks in at start.
Phone: iPhone . Browser: Chrome
bikeID: 3
Comments: It was slow when I was close to someone
Phone: iPhone . Browser: Bluefy
bikeID: 4
Comments: It is awful. I need to bike really hard to catch up after adding the speed control.
Phone: NA . Browser: Chrome
bikeID: 5
Comments: On green the pedal was loose but on blue and red it waa more difficult
Phone: iPhone . Browser: Safari
bikeID: 6
Comments: All is ok.
Phone: iPhone . Browser: Bluefy
bikeID: 7
Comments: Felt lesser effort in the beginning but then had to really push myself towards the end
Phone: iPhone . Browser: Chrome
bikeID: 8
Comments: This is a much different experience. It is easier to ride when you have to catch up after the attracter I almosed crashed another rider towards the end of the ride.
Phone: iPhone . Browser: Bluefy
bikeID: 9
Comments: A little less jerky
Phone: iPhone . Browser: Bluefy bikeID: 1
Comments: NA
Phone: iPhone . Browser: Chrome
bikeID: 2
Comments: fine.
Phone: iPhone . Browser: Chrome
bikeID: 7
Comments: Lost bluetooth connection during ride, apart from this rather pleasant experience and Morningount by effort required was les.
Phone: iPhone . Browser: Chrome
bikeID: 9
Comments: motor is less work, mostly manual pedaling
Phone: iPhone . Browser: Bluefy bikeID: 3
Comments: I was the first one and the bike made me go slower
Phone: iPhone . Browser: Bluefy
bikeID: 4
Comments: It doesn't let me speed up when I'm behind
Phone: NA . Browser: Chrome
bikeID: 5
Comments: The green moced freely but the blue and red had resistance
Phone: iPhone . Browser: Safari
bikeID: 6
Comments: No problem, It was going well
Phone: iPhone . Browser: Bluefy
bikeID: 8
Comments: Very fast pace and more physically demanding
Phone: iPhone . Browser: Bluefy bikeID: 1
Comments: Bike slowed down again and had to go disconnected begore getting back
Phone: iPhone . Browser: Chrome
bikeID: 3
Comments: It is a little frustrating, querer is mmas rapido pero que la bici vaya lento.
Phone: iPhone . Browser: Bluefy
bikeID: 7
Comments: Good. No problems.
Phone: iPhone . Browser: Chrome
bikeID: 8
Comments: This ride was slow but still physically demandig
Phone: iPhone . Browser: Bluefy
bikeID: 9
Comments: lots of motors help during faster prompt no motor help for slower prompt
Phone: iPhone . Browser: Bluefy bikeID: 2
Comments: Fine. Motor didn't do much work this time
Phone: iPhone . Browser: Chrome
bikeID: 4
Comments: I can accererate more when I Morning behind but the motor isn't working that great at rMorningps
Phone: NA . Browser: Chrome
bikeID: 5
Comments: it sloweded me down when I Morning close to the attractor.
Phone: iPhone . Browser: Safari
bikeID: 6
Comments: I had problem with the Bluetooth: the probes is when I connected two devices ( airpods and bike)
Phone: iPhone . Browser: Bluefy bikeID: 3
Comments: Did not hear sound for red and blue, heard for green. Ride went smoothly
Phone: iPhone . Browser: Chrome
bikeID: 4
Comments: I stopped in a ccurve because it was not enough space in the road for all of us, so I was afraid to fall
Phone: iPhone . Browser: Chrome
bikeID: 6
Comments: I fell behind a little
Phone: iPhone . Browser: Safari
bikeID: 8
Comments: When I reach the leader it still advised me to go faster. I think it would be good to adjust the buffer
Phone: Android . Browser: Chrome bikeID: 3
Comments: Stops should be marked on screen, places that have stop signs are not that clearly marked, making it hard to know when stop signs happen. Some sound issues as before
Phone: . Browser:
bikeID: 4
Comments: It feels like the bicycle did not has enough power. I had to stop ones because of a pedestrians
Phone: iPhone . Browser: Chrome
bikeID: 6
Comments: I was matching speed for half the mile, then slowed down to last, and the last 1/4 mile I caught up again
Phone: iPhone . Browser: Safari
bikeID: 8
Comments: This journey was better. I felt that I was clost to the main rider.
Phone: Android . Browser: Chrome bikeID: 3
Comments: Tried to stop screen to enable sound, did not work. Nice and easy speed
Phone: . Browser:
bikeID: 4
Comments: The bike perform was way better, the velocity and the changes in the road was easy ti manage
Phone: iPhone . Browser: Chrome
bikeID: 6
Comments: I was going too fast and had to slow down, but then i was too slow and had to speed up
Phone: iPhone . Browser: Safari
bikeID: 8
Comments: The speed changed a lot. I felt that in many sections of the route, the speed was too low.
Phone: Android . Browser: Chrome bikeID: 3
Comments: is easier to be flocking with this speed.
Phone: . Browser:
bikeID: 4
Comments: I had to push myself more time, to reach the attractor
Phone: iPhone . Browser: Chrome
bikeID: 6
Comments: I was gettng tired and had to go faster for most of the time
Phone: iPhone . Browser: Safari
bikeID: 8
Comments: This journey was much faster. I liked this better. proximity system was better
Phone: Android . Browser: Chrome bikeID: 3
Comments: much more of a physical load, but less of a mental load. Would be better with higher quality bikes with higher gears. sometimes the motor just doesnt work on green
Phone: iPhone . Browser: Bluefy
bikeID: 4
Comments: This time I feel more shifts in the velocity of the bike. Sometimes good velocity and sometimes I had to push more myself.
Phone: iPhone . Browser: Chrome
bikeID: 6
Comments: I was faster and caught on to speed more this time, especially in second half
Phone: iPhone . Browser: Bluefy
bikeID: 8
Comments: This journey was more demanding. It was difficult to keep track
Phone: Android . Browser: Chrome bikeID: 3
Comments: Pedestrians in the road slowed us down. maybe the bike could give assistance when changing elevation as well
Phone: iPhone . Browser: Bluefy
bikeID: 4
Comments: Also feel the shift of velocity in the bike, in some parts of the road I feel more difficult to keep the attractorr
Phone: iPhone . Browser: Chrome
bikeID: 6
Comments: Now I match the speed most of the time
Phone: iPhone . Browser: Bluefy
bikeID: 8
Comments: This journey was ok. I feel that I have to push harder
Phone: Android . Browser: Chrome bikeID: 3
Comments: green had no assistancr after the bottom left corner (near the fab lab) had to bike really fast to catch up
Phone: iPhone . Browser: Bluefy
bikeID: 4
Comments: my iPhone get disconnected from the bluetooth, so I had to stop to reconnect and also the sound did not work in all this trip
Phone: iPhone . Browser: Chrome
bikeID: 6
Comments: I followed the indicated speed a majority of the time
Phone: iPhone . Browser: Bluefy
bikeID: 8
Comments: It was more difficult for me. I feel that I have to use more effort.
Phone: Android . Browser: Chrome