Integrations and data synchronisation

Data has to lead somewhere

An integration has value when it shortens the path to a decision. I therefore look at the API contract, application state, failure handling and the experience of the person using the data together.

Spotinder: a gesture as a shortcut to discovering music

Spotinder combines the card interaction known from dating apps with discovering Spotify artists. Instead of scrolling a long list, the user decides with one gesture and gets immediate feedback.

FIELD NOTE

STARTING POINT

Music discovery should feel engaging

The goal was a lightweight, multiplatform experience: an artist card, cover art, genres and a short preview should be enough to make the user want to see the next suggestion.

MY WORK

Interaction, API and state in one rhythm

I built the card view, like and dislike actions, audio previews and a recommendation queue fed by Spotify data. Moving to the next card had to stay responsive and work with both touch and mouse input.

TECHNICAL DECISION

MVVM keeps logic out of the view

A shared .NET MAUI project, XAML and MVVM separate the artist model, queue state and commands from presentation. ObservableCollection updates the view automatically, while native gestures provide immediate feedback.

Technology follows the constraint.

The stack below is a map of the examples on this page, not a shopping list. I choose only what the problem can justify and what the next person can maintain.

REST
SQL
JSON
Docker