AndeSpace

University spaces went unused, and there was no simple way to book group spaces or to get together with friends based on everyone’s schedule.

Without it, spaces and time are wasted, and groups fail to coordinate because finding a common slot takes too much effort.

Team of 6: three people on the Kotlin app and three on the Flutter app, all of them also on the shared backend and database. Worked on the Flutter app.

My contributions

• Designed and built the home screen, search, classroom booking and the friends network with visibility statuses (busy, at home, free…).
• Each one end to end: brainstorming, design, documentation, database, backend and Flutter.

Team contributions

Teammates built, also end to end, settings, favorites, history, personal schedules, schedule matching with friends, in-app notifications and the room detail view.

Decisions

• Options

  A home screen with many features or only the essentials, and a busy or a restrained design.

  Choice

  A simple home screen and a restrained design.

  Why

  To reduce friction, make the app understandable without explanations and avoid overwhelming its users.

• Options

  Always showing friends or not.

  Choice

  Letting each person decide how visible they are to their friends.

  Why

  Privacy stays in the user’s hands, not the app’s.

Changes of direction

• The social side was not in the original plan. Feedback showed it was essential, because people’s social circle is inseparable from how they use spaces, so the team pivoted to include it.

• Best Project in its section in Mobile Application Development.
• Learned, for the first time, to build one unified backend that serves two different frontends.

Lessons learned

• Would bring the friends and schedules features in much earlier, since they added the most value.