First impression - good and bad
Hi all,
As a newcomer to the Wazeyness I would like to share my thoughts and views on it.
The install was painless - quite excited to get it going, using the mobile to register was the easiest I have ever seen. I sprung in to action and immediately started driving a route where I could do some road munching... strangely satisfying I have to say!
The updates on the screen were quite relevant to the routes I travel regularly. Seeing fellow wazers on the map was awesome and on one occasion I noticed that there was another wazer on the route I use.. so I done some "advanced" driving and caught up with the other user - or so I thought... The GUI said I was next to another wazer.... but there was nothing on the road near me. Later on in the drive, I got the 'Well done, you have travelled your first 5km' .. to be correct it was my first 95KM! I have heard about slow - but that is a bit ridiculous.
Logging on to the web page was easy, but this aspect lets the side down completely. I wanted instant gratification and only to find out that the backend updates every 24hrs up to a week! What on earth are you processing!!! Myself as a user is not impressed by this, and if your data processing is very CPU intensive and long, then LOOK AT IT AGAIN - you have done it wrong! Dont take this as a negative, Rome wasnt built in a day either, but look at what users want and compare to what the goals are... Users want points! and I feel users dont really care that the GPX data takes 2 days to process - and perhaps a two-pass method can be used. (first step is a summary points crediting and KM update; or even let the mobile phone TELL the server the KM travelled, second pass is to get the maps in to the system)
My current listings show that I have done three routes and that 0KM has been travelled - WHY tell me then! Why waste bandwidth to upload the GPX data if the phone was on my desk (or I was most likely tinkering) Some smarts is needed there to remove the rubbish logs.. I would suggest the handset does not update until it has atleast 500m at the start.
Now I have the dashboard covered, the login system is complete rubbish. I login to the Dashboard with my credentials, the Click on Forums and then try post a message - you get presented with a 'You have to be logged in to post messages'; I just DID login!
Overall
Mobile Experience is awesome - Although I drove past a fantom wazer
Web pages look like they are a "Oh Sh.., we need a web page now!"
As a newcomer to the Wazeyness I would like to share my thoughts and views on it.
The install was painless - quite excited to get it going, using the mobile to register was the easiest I have ever seen. I sprung in to action and immediately started driving a route where I could do some road munching... strangely satisfying I have to say!
The updates on the screen were quite relevant to the routes I travel regularly. Seeing fellow wazers on the map was awesome and on one occasion I noticed that there was another wazer on the route I use.. so I done some "advanced" driving and caught up with the other user - or so I thought... The GUI said I was next to another wazer.... but there was nothing on the road near me. Later on in the drive, I got the 'Well done, you have travelled your first 5km' .. to be correct it was my first 95KM! I have heard about slow - but that is a bit ridiculous.
Logging on to the web page was easy, but this aspect lets the side down completely. I wanted instant gratification and only to find out that the backend updates every 24hrs up to a week! What on earth are you processing!!! Myself as a user is not impressed by this, and if your data processing is very CPU intensive and long, then LOOK AT IT AGAIN - you have done it wrong! Dont take this as a negative, Rome wasnt built in a day either, but look at what users want and compare to what the goals are... Users want points! and I feel users dont really care that the GPX data takes 2 days to process - and perhaps a two-pass method can be used. (first step is a summary points crediting and KM update; or even let the mobile phone TELL the server the KM travelled, second pass is to get the maps in to the system)
My current listings show that I have done three routes and that 0KM has been travelled - WHY tell me then! Why waste bandwidth to upload the GPX data if the phone was on my desk (or I was most likely tinkering) Some smarts is needed there to remove the rubbish logs.. I would suggest the handset does not update until it has atleast 500m at the start.
Now I have the dashboard covered, the login system is complete rubbish. I login to the Dashboard with my credentials, the Click on Forums and then try post a message - you get presented with a 'You have to be logged in to post messages'; I just DID login!
Overall
Mobile Experience is awesome - Although I drove past a fantom wazer
Web pages look like they are a "Oh Sh.., we need a web page now!"
Re: First impression - good and bad