Android app parsing JSON from ZTM open data bank and rendering bus stops markers on Google Maps.
LoginActivity- handles user's authentication and acts as launcher activityUserRegistrationActivity- provides interface for user registrationMainActivity- core activity allowing user to select desirable action he/she wants to performTimetableActivity- parses JSONArray into ArrayList object which is loaded into drop down list (Spinner)MapsActivity- initial project's activity parsing JSON and rendering markers based on bus stop's coordinates within Tricity's range
- Firebase authentication module -> user registration and login
- parse JSON data from Tricity ZTM's API and mark down every bus stop within the agglomeration on Google Maps
- (WIP) parse JSON data into selectable Spinner and display bus stop-related timetable grouped by bus' number
-
TimetableActivity->busStopsSpinner -
MapsActivity- extend basic GM markers with additional actions/set of information regarding current bus stop's coordinates - general optimization of JSON parsing process - one of the issues is related to
TimetableActivityparsing same JSON input every time when user leaves the activity and re-opens it, sinceBusStopsobjects cannot be stored insharedPreferences(at least not yet) - minor code refactoring & cleanup
Certain virtual machines struggle with the application, thus some of its features may not work as intended - launching onlineZTM on physical device is the most reliable way of testing it. Currently the only affected modules seem to be LoginActivity and TimetableActivity.
Symptoms:
- user cannot get past Login screen while logging in as Anonymous user (though the job is run correctly in the background- a possible workaround is to hit "Sign in" button, but user will be greeted with "Welcome back, null" - most likely a UI-related bug)
TimetableActivitymay be unresponsive and/or user is immidiately kicked back toMainActivityscreen (no available workaround so far)
Apart from that, sometimes Toast message is triggered more than once - most likely performance-related issue, on physical device it's almost non-existing.
