Skip to content

Cielixir

A web app that recommends a drink based on real-time weather, the user’s cravings and profile.

  • Web development
  • Design & UX
Preview of the project Cielixir

Context

Semester team project of the BUT MMI degree, run with an Agile method: sprints, with a deliverable at each stage. The goal: build a smooth, personalised experience that queries an external weather API and filters a drinks database according to the user’s choices.

My role

Project manager, working in a pair with Ruslana Budniak: Agile coordination (sprints and tasks tracked in Jira), deliverable planning and follow-up through to the final presentation. UX/UI design and development of the app, the landing page and the legal pages.

Context
Semester project (BUT MMI degree)
Team
Pair
Period
March – June 2026

Goals

  • Recommend a drink suited to the weather and the user’s cravings
  • Offer a personalised experience (accounts, favourites, history)
  • Deliver a live app and a promotional landing page

Outcome

A live, working app: real-time weather, a 3-question quiz, a catalogue of 9 categories, user accounts, favourites and history, a landing page and complete legal pages.

<under-the-hood />

Under the hood

Front-end

  • Astro
  • Tailwind CSS
  • JavaScript

Back-end & data

  • PocketBase
  • API Open-Meteo

Design

  • Figma

Deployment & management

  • Jira
  • Git & GitHub

Technical choices

  • Astro for a fast, component-based site
  • PocketBase for accounts, favourites and history
  • Open-Meteo API, free and key-less, combined with geolocation and a city search
  • Tailwind CSS for the interface

Challenges and solutions

  1. bug #1

    Recommendations didn’t work when location access was denied

    Cause: Some browsers or visitors block geolocation

    ✓ fix Solution: A city search added as a fallback to geolocation

  2. bug #2

    Favourites and history had to stay private

    Cause: Without rules, any account could read other users’ data

    ✓ fix Solution: PocketBase access rules: each user only sees their own records

  3. bug #3

    Delivering at every phase as a pair

    Cause: Many parallel tasks and tight deadlines

    ✓ fix Solution: Agile method: work split into sprints, tasks tracked in Jira

Full process

  1. Step 1: Concept

    Market and needs analysis, and concept definition: drink recommendations based on weather and geolocation.

  2. Step 2: Concept presentation

    Presentation and defence of the concept to the jury.

  3. Step 3: Research and mockups

    Sitemap, wireframes and interactive Figma prototype: weather detection, drink cards, filters, favourites and history.

  4. Step 4: Mockup presentation

    Defence of the UX/UI choices and integration of the jury’s feedback.

  5. Step 5: Development

    Responsive web app: real-time weather API, geolocation, filters, favourites and history stored in PocketBase.

  6. Step 6: Final presentation

    Live demo of the app and project management review.

What I learned

Being project manager taught me to break work down into deliverables and to anticipate delays rather than suffer them.

If I did it again, I would set up code reviews between the two of us earlier.

Project preview

The site runs live on all three devices. Click a device to browse inside it.

Open the site in a new tab ↗