Lending library

Solo project
My role
Duration
Tools

Full development of a digital platform: Market analysis, Strategy design, Web design for Desktop and Mobile, MVP development

1.12 2025 – 27.01 2026

Figma, Tokens Studio, Lovable

PROJECT OVERVIEW
 

The project started with Ben Lingel’s idea to expand the sharing beyond its traditional form. The goal was to bring the local community together by not only distributing movies or books they love, but also tools or plants. This was a system applied in Nuremberg for a group of about half a thousand users. 

An important notion was leaving a review for each of the objects shared in this indefinite space, as it gave all of the items an emotional aspect, differentiating this web-native platform from all of the others already existing.

MY CONTRIBUTIONS
 

I worked as the sole product designer, responsible for the end-to-end process, translating an abstract concept into a live platform. I was deeply involved in strategic decision-making, helping to define the project’s scope under strict budget constraints.

I conducted foundational user and founder interviews to uncover psychological barriers, developed the information architecture, and created both the UX flows and the final, minimalistic UI. I also utilized AI-assisted coding tools to rapidly prototype and launch the platform.

 
PROBLEM
 

1. Abstract concept in need of design translation and infrastructure

2. High traffic, but low content creation rate which caused low retention rate, caused by lack of trust between the users

3. Budget and time constrains

 
SOLUTION
 

1. Creating trust signals in the form to reduce transaction anxiety

2. Implementing an „Intent-Based” categorization system

3. Using AI coding platform to launch functioning platform, reducing ~70% Time-to-Market 

 
 
IMPACT
Est. MRR
Time to Market (TTM)
Retention rate

+2k 

– 70%

+80% 

Key Design Decisions

PROCESS OVERVIEW

Few steps from the process of creating online platform.

DISCOVERY

FOUNDER and USER interviews

I wanted to genuinely grasp the whole idea behind the platform, so that I could successfuly implement it. This project thought me translating concepts into working solutions. It was a lesson into making ideas a reality. It gave me a possibility of building infrastructure for a community.

DISCOVERY
DISCOVERY

RESEARCH SYNTHESIS

With raw data collected, I distilled the findings into actionable insights and defined the core use cases that would drive the architecture:

  • The Protective Lender: Wants to share a beloved plant or expensive drill with the community but needs a guarantee that the borrower understands the specific care instructions before initiating contact.
  • The Anxious Borrower: Needs a tent for one weekend. Wants to browse available items and accept clear terms without the awkwardness of negotiating a favor with a stranger.

DISCOVERY
DEFINITION

IDEATION

The ideation phase was strictly focused on translating our „Trust Economy” hypothesis into scalable Information Architecture (IA). 3 possible solutions to this problem were taken into consideration, with their consequences, advantages and disadvantages:

  • Fully automated data, meaning platform with visable availability, calendar and online map,
  • Partial automation of the data, incorporating forms as communication possibility and the location being filled in by users,
  • No automation of data, inviting to traditional form of communication by mail and no information of the location of the object, before the contact.

 

DEFINITION
DEFINITION

Information Architecture

I have created the option optimizing the best solution, by taking into consideration the users and business expectations.

  • Personal contact: Users were strongly in favour of keeping direct connections by filling in their emails on platform.
  • Structured Metadata: Location of objects was included in specific input fields, connected with other information needed to borrow item like 'Minimum Engagement Time’ and 'Lending Conditions’. This managed user expectations upfront.
  • Card-Based Hierarchy: I used a clean, high-contrast card layout to make the content scannable. I categorized items by User Intent (e.g., 'Something to care for’ vs. 'Something to read’) rather than just media type, which aligns better with the user’s mental model. It was more scalable and accesible then categorization based on map or availability.

DEFINITION
DEFINITION

STRATEGY

I have set clear KPI’s that were followed by design decision to manage clients expectations.

DEFINITION
DELIVERY

WEBSITE DESIGN

I have created a few low-fidelity sketches to design the user experience of the website. Then I have  mastered the UI to match the topic of presented concept, and coded with help of AI ensured quick development and live testing the platform.

DELIVERY
DELIVERY

USER TESTS

Although the first MVP included the  possibility of adding podcast, users were reluctant to post the audio version of their reviews, which has caused the iteration of the web character.

First MVP:

After Iteration:

 

The test uncovered also the need of users to add edits to their profiles or come back to the deleted reviews, which resulted in incorporating functionalities like trash bin or settings.

DELIVERY
DELIVERY

KEY FINDINGS

This platform has uncovered the importance of creating the right infrastructure, that directly impacted the success of the project and tightened the community.

  • Trust signals allowed users to add high quality content and take part in transactions.

 

  • Using actionable verbs in the navigation (e.g., „something to read”) instead of typical nouns, proved that copywriting is one of the most powerful structural tools in a designer’s arsenal.

 

  • Working under constraints showed me that AI coding platforms can be utilized to check the solution on users quicker then traditionally. It only solved our budget constraints but also taught me how to design with extreme technical efficiency in mind, bridging the gap between product conception and market validation.

 

  • Maintenance and habitual usage of this platform was one the key factors, that meant pursuing more traditional form of communication among the users. It showed that sometimes modern fancy solutions, like incorporating availability filters or map do not work in real communities.

 

 

 

 

 

 

DELIVERY
Przewijanie do góry