Results of the testing

All participants stated the application is easy to use as whole. Most of the problems were associated with actions positioned in the action bar, the participants were focused on the main content of the screen and might have overlooked these actions. They also stated that if the my location button was positioned near the start input field it would be easier for them to associate it with setting the current location. The same applies to the flip points action. The participants also liked the suggestions because they did not have to type the whole name of the street.

5.2. APPLICATION TESTING

40

Chapter 6

Conclusion

In this Bachelor’s project I have designed a journey planner application for cyclists. The application is intended to be used only in Prague. It uses Open Bicycle Trip Planner for route planning and for navigation instructions.

The main part of the application is the planner which enables users to select start and finish point of the journey. The profile of the route can be further customized to meet users’ specific requirements. The application contains a database of Prague street names that are used as suggestions to make it easier for users to set journey’s start and finish points. Also the points can be set from the map so users can specify a precise location in Prague and they do not depend on predefined locations. The individual locations and users’ favourite places can be saved in the application so that the process of setting the start and finish points can be speeded up.

The application visualizes the found route in three different ways. The first way displays the route on the map where different types of route are drawn in different colours so users can see where they are supposed to ride on the road or cycleway. The second way displays route itinerary which is a list of individual turn-by-turn instructions with information about where to turn, which street to turn to and how far it is to turning. The third way displays the elevation profile of the route. The profile is visualized in graph so users can see where on the route they will have to go uphill or downhill.

The last important part of the application is the navigation. Users can see their progress on their journey because the application tracks their movement. The navigation also displays instructions to help users with orientation on their ride. The itinerary is also accessible from the navigation so users can easily check several successive instructions.

During the design process the application was tested by real users and their requirements were considered in order to improve the usability of the application.

The current application implementation is in some ways limited. Users can choose only from three different profiles for routing that correspond to profiles used in OBTP. The map bases might not correspond with real situations because Google Maps are used and they are not intended for cyclists. The turn-by-turn instructions or manoeuvres may be wrong in some cases because the instructions are derived from OSM data that may not be complete or accurate.

The application can be improved further. The problem of the bad map bases could be solved by using vector map bases containing information for cyclists but currently there is no map SDK for Android that could provide all important features for the application without bugs and ensure absolute functionality without crashes. A new custom map

SDK would have to be implemented in order to provide the application with a completely functional SDK. At the same time if vector map bases would be used the connection to the Internet would not be required during the navigation. The profiles that users can choose could be more extended so users have more than three profiles to choose from.

This extention would have to be a result of disscusion with OBTP developers so more profiles that are different enough from each other could be provided.

42

References

[1] Android Developers. url: http://developer.android.com/index.html (visited on 04/25/2014).

[2] Android GraphView. url:http://android-graphview.org/(visited on 04/26/2014).

[3] Auto*Mat. Pr˚uzkum cyklistick´ych preferenc´ı ze z´aˇr´ı 2012. 2013. url:http://www.

auto-mat.cz/wp-content/uploads/2013/04/cyklopr%C5%AFzkum_2012_re%C5%

A1er%C5%A1e.pdf.

[4] BikeCityGuide. url:http://www.bikecityguide.org/ (visited on 04/26/2014).

[5] I.G. Clifton. Android User Interface Design: Turning Ideas and Sketches into Beau-tifully Designed Apps. Usability. Pearson Education, 2013. isbn: 9780133154818.

[6] Cyclestreets. url:http://www.cyclestreets.net/(visited on 04/26/2014).

[7] Google Developers. Google Maps Android API v2. url: https : / / developers . google.com/maps/documentation/android/(visited on 04/26/2014).

[8] V. Filler. Dotazovac´ı pr˚uzkum cyklistick´ych preferenc´ı - anal´yza v´ysledk˚u. 2010. url:

http://prahounakole.cz/wp-content/pnk/uploads/2010/10/cyklopruzkum_5_

2010_1.1.pdf.

[9] J. Gilfelt. Android SQLiteAssetHelper. url: https : / / github . com / jgilfelt / android-sqlite-asset-helper(visited on 04/26/2014).

[10] E. Hellman. Android Programming: Pushing the Limits. Pushing the Limits. Wiley, 2013. isbn: 9781118717356.

[11] MapQuest. url:http://developer.mapquest.com/(visited on 04/26/2014).

[12] Mapsforge. url:https://code.google.com/p/mapsforge/(visited on 04/26/2014).

[13] R. Meier. Professional Android 4 Application Development. ITPro collection. Wiley, 2012. isbn: 9781118237229.

[14] M. N´emet. “Open Bicycle Trip Planner”. Bachelor Thesis. Czech Technical Uni-versity in Prague, 2013. url: https : / / dip . felk . cvut . cz / browse / pdfcache / nemetma1_2013bach.pdf.

[15] G. Nudelman. Android Design Patterns: Interaction Design Solutions for Developers.

Wiley, 2013. isbn: 9781118417553. url: http : / / books . google . cz / books ? id = Ifg1ZpSo7cwC.

[16] Nutiteq. url:http://www.nutiteq.com/(visited on 04/26/2014).

[17] OsmAnd. url:http://osmand.net/(visited on 04/26/2014).

[18] OSMBonusPack. url: https://code.google.com/p/osmbonuspack/ (visited on 04/26/2014).

[19] Osmdroid. url:https://code.google.com/p/osmdroid/(visited on 04/26/2014).

REFERENCES

[20] B. Phillips. AndroidCourseResources. url: https://github.com/bignerdranch/

AndroidCourseResources (visited on 04/26/2014).

[21] J. Pucher and R. Buehler. City Cycling. MIT Press. isbn: 9780262304993.

[22] K. Sawicki. http-request. url: http://kevinsawicki.github.io/http-request/

(visited on 04/26/2014).

44

Appendix A

Contents of the CD

<dir> apk -- contains apk file of the application

<dir> prototype -- contains low-fidelity prototype of the application

<dir> source codes -- contains source codes of the application

<dir> thesis-latex -- contains latex version of the thesis

<dir> thesis-pdf -- contains thesis pdf file

Appendix A: Contents of the CD

46

Appendix B

Prototype questionnaire

Experiment – Prototyp mobiln´ı navigace pro cyklisty

17. 2. 2014 Participant:

Demografick´e ´udaje

• vˇek

• pohlav´ı

J´ızda na kole

• Jak dlouho jezd´ıte?

• Na ˇcem jezd´ıte?

(silniˇcn´ı/horsk´e/citybike/silniˇcn´ı/trackov´e kolo, elektrokolo, lehokolo/kolo/kolobˇeˇzka)

• Jak ˇcasto?

• Styl j´ızdy podle:

– povˇetrnostn´ı podm´ınky – ter´en

– kvalita silnic – profil trati – hustota dopravy – profil kˇriˇzovatky – stoup´an´ı

– vzd´alenosti

– klasifikace pˇrek´aˇzek

• Kam? (Popsat detailnˇeji trasu – vzd´alenost, vlastn´ı trasa, ˇcetnost, alternace trasy, zast´avky na trase, r˚uzn´e trasy tam a zpˇet?)

• Kolik tras zn´ate?

– Mate nov´e nebo pravideln´e trasy, pro kter´e si trasu mus´ıte napl´anovat?

Appendix B: Prototype questionnaire

– Potˇrebujete se pod´ıvat nˇekdy do mapy (do instrukc´ı) na info o trase?

Pl´anov´an´ı tras a navigace

• Pl´anujete si trasy a jak?

– Pl´anujete dopˇredu nebo aˇz “u kola”

– Pouˇz´ıv´ate nˇejak´e aplikace? Popiˇstˇe pˇresnˇe, jak je pouˇz´ıv´ate.

• Pouˇz´ıv´ate nˇeco na trase (jak se navigujete)?

– aplikace

Co byste ocenili pˇri pl´anov´an´ı a pˇri j´ızdˇe, aby to bylo:

• komfortnˇejˇs´ı

• bezpeˇcnˇejˇs´ı

• rychlejˇs´ı

48

Appendix C

Testing tasks

1. Chcete si napl´anovat novou trasu.

2. Jako startovn´ı pozici si chcete nastavit Vaˇsi aktu´aln´ı pozici.

3. Rozmysleli jste si startovn´ı pozici, nyn´ı chcete zaˇc´ınat v ulici Technick´a.

4. Jako sv˚uj c´ılov´y bod si chcete nastavit Karlovo n´amˇest´ı s ˇc´ıslem popisn´ym 13.

5. Nikam neposp´ıch´ate, nem´ate r´adi ruˇsn´e ulice, a tak si nastav´ıte odpov´ıdaj´ıc´ı profil trasy.

6. Vyhledejte trasu.

7. Zjistˇete, jak je trasa dlouh´a a za jak dlouho byste se mohli dostat do c´ıle.

8. Je moˇzn´e, ˇze se na trase setk´ate s nˇejak´ymi obt´ıˇzemi. Zjistˇete, jak´e obt´ıˇze to jsou.

9. Z mapy zjistˇete, po jak´em typu cesty pojedete nejˇcastˇeji.

10. Zjistˇete, v jak´e vzd´alenosti od startu budete proj´ıˇzdˇet ulic´ı U P´ıseck´e br´any.

11. Zjistˇete, kolik metr˚u celkem pojedete po cyklostezk´ach.

12. Zjistˇete, v jak´e vzd´alenosti od startu se budete nach´azet v nejvyˇsˇs´ı nadmoˇrsk´e v´yˇsce a jak´a v´yˇska to je.

13. Nyn´ı trasu nechcete absolvovat, ale chcete si ji uloˇzit pro pozdˇejˇs´ı pouˇzit´ı. Uloˇzte si trasu.

14. Zobrazte znovu tuto trasu.

15. Pˇrepnˇete se do navigace.

16. Spusˇtte navigaci.

17. Nejste si jisti, jak d´ale pokraˇcovat, zobrazte si itiner´aˇr a prohl´ednˇete si n´asleduj´ıc´ı instrukce.

18. Pˇredˇcasnˇe ukonˇcete navigaci.

19. Zjistˇete, kolik kilometr˚u jste skuteˇcnˇe ujeli.

Appendix C: Testing tasks

20. Z´ıtra chcete navˇst´ıvit Planet´arium. V´ıte, ˇze se Planet´arium nach´az´ı v ulici Kr´alovsk´a obora 233. Uloˇzte si toto m´ısto, abyste ho mohli z´ıtra jednoduˇse pouˇz´ıt pro vyhled´an´ı trasy.

21. Nach´az´ıte se u Planet´aria a chcete napl´anovat trasu zpˇet tam odkud jste pˇrijeli.

22. Smaˇzte Planet´arium z uloˇzen´ych m´ıst.

50