Problem Definition
Because the feature was a byproduct of the homepage concept redesign, it was constrained in development scope, but laid the foundations for personalized experience and easier navigation
Process
Public Transport Data Structure
The data structure users interact with on public transportation is:
📍 1. Destinations (to reach a destination, user needs a route)
🗺️ a. Routes (a route consists of walking / commuting /waiting legs etc..)
🚏 i. Stations (bus station / metro station... Each station has lines)
🚌 1. Lines (line 1, 238, 501... Each line has trips)
🗓️ a. Trips (a trip has a direction and a time. Example: line 1 to Tel Aviv at 10:07)
Note: This is a general structure.
There can be additional sub-data set such as line-updates, arrival times, route changes, payments etc.
👨💻
Coming soon! I'm still working on this one
Problem Definition
Because the feature was a byproduct of the homepage concept redesign, it was constrained in development scope, but laid the foundations for personalized experience and easier navigation
Process
Public Transport Data Structure
The data structure users interact with on public transportation is:
📍 1. Destinations (to reach a destination, user needs a route)
🗺️ a. Routes (a route consists of walking / commuting /waiting legs etc..)
🚏 i. Stations (bus station / metro station... Each station has lines)
🚌 1. Lines (line 1, 238, 501... Each line has trips)
🗓️ a. Trips (a trip has a direction and a time. Example: line 1 to Tel Aviv at 10:07)
Note: This is a general structure.
There can be additional sub-data set such as line-updates, arrival times, route changes, payments etc.
👨💻
Coming soon! I'm still working on this one
