Lens90 match page on a phone and desktop

Case study

Lens90

Lens90 – live at lens90.com

Football fans who want a probability, not a tip, have no way to tell which prediction site to trust, so Lens90 makes trust the main feature.

Status
In production since October 2026, live at lens90.com
Role
Product, UX/UI and graphic design, product direction
Team
Houtan Ghazi (design and direction), Rojiar (German and Persian wording)
Languages
English, German, Persian (right-to-left), same pages in all three
Coverage
35 competitions. On 11 Nov 2026 the matches list held 249 upcoming matches in 24 leagues
Scale
About 1,840 static pages in the latest release, plus the app
Channels
Website, Instagram, Telegram, YouTube, TikTok, each in three languages

Visit lens90.com

What a visitor gets

In the order the product shows it: a featured match, the top tips of the day (only when they pass a strict check), the model's public record, a filterable list of upcoming matches, league matchday pages, and short plain-language answers to the questions a newcomer asks.

The design idea behind all of it is simple. A prediction product is believable only if its interface is honest. So the screens show hits and misses side by side, treat the empty day as a feature, and keep the same structure and numbers in all three languages.

Discover

Problem and users

Who the product is for, and why they would not trust it yet.

Football fans who want a probability rather than a tip have no way to tell which prediction site to trust, so Lens90 makes trust the main feature.

A competitor review on 25 October 2026 found sites in this space with accuracy claims that contradicted each other (78%, 56%, 58% and 9% on different pages), no published track record, and everything framed as tipster advice. Most are English-only. German and Persian speakers follow the same leagues and are rarely served in their own language.

Three personas came out of that, each with one question they bring and ten seconds to get an answer. They are inferred from how the product is built and used, not from interviews. They are a starting point to validate, and the case study says so.

Persona 1, the match-day checker, on a phone an hour before kickoff. Question: who is the favourite tonight? Success looks like three percentages and a colour bar, no scrolling.
The match-day checker needs the answer before any scrolling.
Persona 2, the skeptic, arriving from search or a friend. Question: is this real? Success looks like hits and misses both visible, by pick type, for yesterday, 7 and 30 days.
The skeptic needs proof, so the record shows misses too.
Persona 3, the social follower, arriving from a daily post in German or Persian. Question: where are the picks from the post? Success looks like the same structure and tone in all three languages, right-to-left done properly in Persian.
The social follower expects the landing page to match the post, in the same language and direction.

Define

Jobs to be done

What they need to get done, and the paths that get them there.

JobWhenWhere it is solvedSuccess looks like
See the odds of tonight's match at a glanceBefore kickoffFeatured match card, match pageThree percentages and a colour bar, no scrolling
Find the few picks worth attentionMorning of match dayTop tips of the dayA short list, or an honest "no picks pass the check"
Judge whether the model is any goodFirst visit, or after a missTrack record, "The model, on record" blockHits and misses both visible, by pick type, for yesterday, 7 and 30 days
Browse by league or dayPlanning the weekendUpcoming matches with league and date filters, matchday pagesAny league's round on one page
Understand what a number meansWhenever a term is unclearFAQ, methodology, fair odds explainerAn answer in two sentences, in the visitor's language
Follow in their own languageDailyEN, DE, FA versions, social channels per languageSame structure and tone in all three, right-to-left done properly in Persian

User journeys

For each persona I mapped where they arrive from, where they should land, and what comes next. The match-day checker lands on the home page and goes on to the match overview if they want more. The skeptic lands on the track record and goes on to the latest checked picks, misses included, and the methodology page. The social follower taps a link in a post and lands on the day's picks or results in the same language and direction, with the record one tap away.

Journey map with three rows. Match-day checker: opens the home page, sees the featured match with home win, draw and away win, then the match overview. Skeptic: arrives from search or a shared link, lands on the track record, then the latest checked picks and the methodology page. Social follower: taps the link in a post, lands on the day's picks or results, then the record one tap away.
From first tap to the answer, one row per persona. Routes as shown on lens90.com.

Information architecture

Five sections and two fixed bars: Home, Matches, Predictions, Leagues and Track record, with the header on every page and a footer that repeats the trust pages. Detail pages (match and result) are reached from every list.

The one choice that shaped the map is that the trust pages are never more than a tap away. Track record is its own section and also sits in the footer next to the methodology page, so a visitor who doubts a number can check it from anywhere.

Site map. A header on every page with logo, language EN / DE / FA, theme and menu button. Five sections: Home, Matches, Predictions, Leagues and Track record, which is highlighted. Below them detail pages reached from every list, and a footer with Track record, Methodology, Site map, Imprint and Privacy settings.
The trust pages are one tap from anywhere.

Design

Wireframes, mobile first

Screens, rules and a system that keep the answer in the first ten seconds.

I drew the five key screens as phone layouts first, since the match-day checker has a phone in hand an hour before kickoff. A few rules ran through all of them.

Every block has one action. The answer comes before any scrolling: three outcomes and a colour bar, in the same place on the home page and the match page. The page title on the track record is the visitor's own question, "How often were the Lens90 picks right?", followed by one sentence with the 30-day numbers. Hits and misses share one row layout, so a miss gets no more and no less weight than a hit. Long lists use "Show more" instead of endless scroll, so the footer and the trust pages stay reachable.

Wireframes 1 of 3, home. Top of page: header, featured match with three outcomes and a colour bar, one action, and top tips of the day with its rule stated. Further down: the model on record with a period switch, hit rate tiles, hits and misses in one row layout, and upcoming matches with search and filters.
Home. The top tips block states its rule even when it has no picks.
Wireframes 2 of 3, match page and top picks. Match page: breadcrumb, title, result probabilities with a colour bar, one plain sentence on what the model expects with a confidence grade, and a reminder line. Top picks: title with a subtitle that states the rule, one card per match, next matches and FAQ.
Match page and top picks.
Wireframes 3 of 3, track record and matches list. Track record: question as title, one sentence with the 30-day numbers, hit rate by type of pick, latest checked picks with right and wrong labels, and how the record is kept. Matches list: count, search, league, date and sort, match cards with home, draw, away and a confidence grade, and show more.
Track record and matches list.

Design decisions

Phone first

Mobile first is the biggest design decision. The match-day checker has a phone in hand an hour before kickoff, so every layout starts at phone width (390 px) and desktop comes second. The wireframes here are phone layouts, and layout shift is measured at phone width as well.

Designed states

The empty and uncertain moments are where trust is won, so each one has its own copy and rule. On a day without picks the screen says "No picks pass the check right now" and then states the rule.

No verdicts

Each match gets three outcome cells and a bar. Fair odds are labelled as 1 divided by the chance, and an ODDS badge marks numbers that come from bookmaker prices.

Colour carries meaning

Home, draw and away have their own colours, separate from right and wrong. A green bar for a home win never reads as "correct", and either set can change without touching the other.

A name that cannot be misread

The working name carried the word "bet", which ad networks and payment providers can read as gambling. It became Lens90 on 6 October 2026.

Brand and social

Wordmark in day and night versions, favicon and share image, profile tiles for each language, and templates for the daily social posts. The same saved predictions feed the website, Instagram, Telegram, YouTube and TikTok, so a number never differs between channels.

States designed on purpose
StateWhereWhat the screen says or does
No picks todayTop tips of the day"No picks pass the check right now", then the rule: probability above 70%, fair odds at least 1.25, bookmaker odds agree
No tips in the next 7 daysTop picks"No tips above 65% in the next 7 days", with a sentence on when they appear
Prediction pendingMatch page, match cards"Prediction not yet available" instead of a number
Odds-based numbersMatch cards, match pageAn ODDS badge, and the methodology page explains that these competitions use bookmaker prices
ConfidenceMatch cardsA Low, Medium or High grade next to the leading probability
Played matchResult and matchday pagesFinal score next to the saved prediction, with a right or wrong label
Not foundUnknown addressA notice page inside the same shell, with header and footer

Design system

One green accent on a calm grey-blue ground, in a light and a dark theme chosen from the header. A darker green is used for text on light backgrounds so it stays readable. The type is Inter in six sizes from 14 to 34 px, with body at 16 px and a line height of 1.5.

Spacing runs on a scale of 4, 8, 12, 16, 20, 24, 32, 40, 48 and 64 px, and an automated test fails the build on a stray value. A spacing pass on 30 October moved card margins from 10 and 18 px to 12 and 16 px to fit the scale. Buttons are 44 px high.

Design system sheet. Colour in light and dark themes: page, surface, text, muted, border, accent, accent text and hero. Forecast colours for home, draw and away, status colours, the Inter type scale, the spacing scale, radius steps and components: probability bar, confidence badges and buttons.
Colour, forecast colours, type, spacing and the main components.

Three languages, one structure

English, German and Persian pages share routes, blocks and numbers. Persian runs right-to-left throughout, inside a layout that was drawn left-to-right first, so the cards, bars and tables were checked in both directions.

Rojiar, a native German and Persian speaker, reviewed the wording. On 29 October we changed the German "Tipps" to "Prognosen" (Top-Prognosen, Prognosearten, Prognosen für heute), because "Tipps" sounds like a betting tip and the product is not one.

Deliver

The live product

What is live, what the numbers say, and what comes next.

These are the live screens, captured on 15 November 2026 at phone width (390 px), in the dark theme. The home screen leads with the featured match: three probabilities and a colour bar before any scrolling, then the day's top tips with an ODDS badge where a number comes from bookmaker prices.

The match page repeats the same three cells and adds the model's confidence and data quality. When confidence is missing it says "Not available" instead of hiding the row.

Lens90 home on a phone in the dark theme. Header with logo, language, theme and menu. Featured match Bayern against Köln with home win 88.9%, draw 8.2%, away win 2.9%, a colour bar and a featured tip. Below it the top tips of the day with ODDS badges.
Home: the answer first, then the day's picks.
Lens90 match page on a phone in the dark theme. Breadcrumb, pre-match analysis card for Bayern against Köln with the three probabilities, model confidence shown as Not available, and data quality 100% Strong. Tabs for Overview, Teams and Analysis.
Match page: the same three cells, with an honest empty state for confidence.

Then desktop

On a wide screen the same blocks sit in rows and the navigation moves into the header. The match page keeps its three tabs: Overview for the result and double chance, Teams for the signals behind each side, and Analysis for the written reasons and the evidence.

Lens90 match page on desktop, Overview tab, in the dark theme. Pre-match analysis card with Coritiba 36%, draw 29%, Santos 35%, model confidence Low 37% and data quality 88% Good. Below, match result bars, double chance and match intelligence.
Overview tab.
Lens90 match page on desktop, Teams tab, in the dark theme. Home and away team profiles side by side with attack, defence and form, attacking and defensive signals as small tiles.
Teams tab: both sides next to each other.
Lens90 match page on desktop, Analysis tab, in the dark theme. Match intelligence headline, prediction context bars, and home and away analysis with strengths, weaknesses and context.
Analysis tab: strengths, weaknesses and context in plain sentences.

Results so far

Lens90 can be defended on process rather than on one result. Every forecast is written down before kickoff, every checked pick is listed, and the interface says plainly when there is nothing to recommend.

On 11 November 2026 the track record page showed 303 top picks checked in the last 30 days, 241 of them right (80%). Picks follow a rule the site states in public: a model probability above 70%, fair odds of at least 1.25, and bookmaker odds that agree where they price the match. Double chance is a low-risk pick type, so 80% does not mean the model predicts matches 80% of the time. It means top picks that passed the rule.

A 30-day window is short, so the figure shows that the method is visible, not that it is proven. On the quality side, a real-browser check on 10 November 2026 measured layout shift at 0.035 on desktop and 0.06 on a phone. The site is early, so there is no traffic figure here to lead with.

Top picks by type, last 30 days (track record page, 11 November 2026)
Pick typeCheckedRightShare
Double chance19415680%
Match result292276%
Goals, over/under 2.5635079%
Handicap171376%

What I would do next

Validate the personas with real visitors, add more leagues, and make delivery more reliable. Publishing to the social channels needs retries and alerts, because a gap from 12 to 15 November showed what happens without them.