Valeria Shulakova · Senior product designer
Own productExpatly · iOS · 2024 — Present

Turning visa and tax-residency rules into a calm daily tracker

My own iOS app for people who live between countries. It keeps a record of days spent in each country and answers what depends on it: tax residency, residence permits, Schengen trips.

Live on the App Store · v1.3.0
Role
Product designer and owner: strategy, research, monetisation, UX, UI, brand
Team
Me and one iOS developer
Timeline
2024 — present
Launched April 2025 · Pro July 2026 · v1.3.0
Platform
iOS (iPhone), designed for iOS 26
Status
Live · 5 languages
Problem

People who live between countries count days by hand, in notes and spreadsheets. A wrong count can cost a permit, a visa or tax residency.

Solution

One travel history, filled in mostly automatically and easy to correct, behind every answer the app gives: statistics, personal limits, Schengen planning.

Outcome

Live since April 2025 in five languages, with paying users in several countries.

Product tour

The app in motion

Context

The history is the hard part, not the rule

Expats watch tax-residency thresholds, often around 183 days a year, and minimum stays for residence permits. Digital nomads juggle a limit in every country they pass through. Travellers on Schengen visas need to know whether the next trip fits the 90/180 rule.

I live abroad myself and started from my own spreadsheet. Then I talked to expats and digital nomads and reviewed the main day-counting apps and their user reviews. Three findings set the direction:

1The history is the hard part, not the rule

People know their limits but rebuild their travel from memory right before a deadline.

2Automation alone isn't trusted

GPS-only apps miss flights and drain the battery, and users want to correct what the app records.

3A bare number causes worry

A total without the trips behind it is hard to rely on.

Product strategy

One goal: calm control

Day-counting is about real risks, so I set one goal for the product: calm control.

One history behind every screen

Fix a date once, and statistics, the map, limits and the Schengen planner all update.

Automation stays correctable

Found trips are reviewed before saving, and any automatic check-in can be edited or removed.

Every number opens up

A total shows its trips; a rule shows its source.

SOURCESManual check-inLocationPhoto scanImportOne travel historyfix a date once, every view updatesVIEWSCalendarCountriesMapANSWERSLimitsSchengen plannerOUTPUTSShare cardsExport
01
Key decision · Data sources

Three sources, one review step

Problem

New users arrive with months of travel to log. Asking them to type it loses them; trusting a single automatic source loses accuracy.

Decision

I gave three sources separate jobs: a two-tap check-in for today, location for the present, an on-device photo scan for the past. Photo scans and file imports end on a review screen, where nothing is saved until the person confirms it.

A location check-in asks before saving today's country; background check-ins, once switched on, run on their own and can be corrected later. Each permission request is preceded by a plain explanation of what the app reads, and a refused permission leads to an alternative, not a dead end.

Why

Each source covers another's gaps, and review appears where errors are most likely — in bulk imports of the past.

In motionFrom a camera roll to a travel history
1

The scan finds 29 photos taken abroad

2

Found trips wait on the review screen

3

One tap adds 25 days in 4 countries

4

The home screen shows the new days

1First launch
No trips yet
→
2Photo scan
Found trips wait for review
→
3Confirmed
Months of travel in one step
Source 1Manual check-in
Add a country and a date in two taps
Source 2Location
Detects the current country and asks before saving it
Source 3Photo scan
Finds past trips from photo dates and places, on the device
ResultThe review screen became a reusable pattern: imports from other apps and from backups later shipped on it with no new UI.
02
Key decision · Rules

One model for every limit

Problem

Users asked to track more than Schengen: tax residency, permit requirements, personal goals. A separate calculator for each rule would not scale, and a generic rule builder would be too hard to set up.

Decision

I reduced every rule to four parts — country, direction, number of days, period — and made it read as a sentence: “No more than 183 days this year”. Presets fill the sentence for common cases and show the official source, what the rule does not cover and when it was last checked.

In motionSetting up a tax-residency limit
1

Tap “+ Limit” and pick Canada

2

A preset explains the rule, its source and what it doesn't cover

3

“Fill the form” turns it into a limit

4

The card appears on the home screen

The rule editor
The rule editor reads as a sentence
A preset, annotated
123
1
The rule as a sentence

“No more than 183 days this year”: what is counted and against what, readable without the law in front of you.

2
The official source

A link to the government page, so anyone can check the rule themselves.

3
What it doesn't cover

Days are only one of the residency criteria. The card names the others, so staying under the limit isn't read as “you're not a tax resident”.

Decision 02 · detail

The home-screen card

The home-screen card took the most iterations. It had to work both for a ceiling, where going over is the problem, and for a floor, where staying under is. In the first version the bars were hard to read: it wasn’t clear what the colours and the marker meant. After several rounds of palettes, layouts and edge cases, both types share one bar whose colour means only “on track” or “not”.

1Iteration 1
Direction in words: “from 183”, “up to 18”
→
2Iteration 2
Direction as arrows next to the number
→
3Released
One bar, a ≤ or ≥ threshold and a status colour
A · Flag in a ringA · Flag in a ring
B · Card as a barB · Card as a bar
C · Full-width rowC · Full-width row
Explored layouts
Three layouts explored: A — the flag as a ring, B — the card fills up like a bar, C — a full-width row. None shipped as is: the release kept the two-column grid and took the bar with a dot marker.
From the iterations
Status and number coloursStatus and number colours
No more than ≤ 183No more than ≤ 183
At least ≥ 183At least ≥ 183
Palette K1: the number changes colour as it nears the limit
ResultOne model covers tax thresholds, permit requirements and Schengen. Limits ship in 1.3.0 as a Pro feature, with presets and their explanations translated into five languages.
03
Key decision · Schengen

A Schengen calculator that plans ahead

Problem

Most Schengen calculators answer “how many days have I used”. The question travellers actually have is “will my next trip fit” — and visa holders also depend on the visa's dates and number of entries.

Decision

I built the calculator around planned trips. It collects the visa details step by step, takes past trips from the existing history instead of asking for them again, and gives every planned trip a clear verdict.

Special cases, such as an expired visa or a used single entry, appear as plain messages rather than a confusing number.

In motionChecking a future trip
1

Open the Schengen card

2

Add a future trip: Croatia, 20–28 November

3

The calculator checks it against the 90/180 rule

4

The verdict: “Trip allowed”

Visa details, step by step
Past trips come from the history
A verdict for every planned trip
Expired visa — a plain message
Single entry already used
ResultPlanning a trip takes a few answers about the visa, with no re-entry of past travel.
04
Key decision · Monetisation

Free answers, paid automation

Decision

The app was free for its first year. Pro arrived in version 1.1.0, and basic counting stayed free: someone checking whether they can stay a few more days should get that answer without paying. So Free covers manual and location check-ins, the history, short periods and the Schengen calculator. Pro sells time saved and depth: background check-ins, the full photo scan, long and custom periods, limits and export formats.

The photo scan is the strongest argument for Pro, so Free includes a 30-photo trial that shows a person their own trips before the paywall. Ending Pro deletes nothing; limits wait until Pro returns.

1.1.0
Annual, monthly and weekly subscriptions
→
1.3.0
“Pro forever” by default, no weekly plan
A 30-photo trial before the paywall
“Your limits are saved” after Pro ends
Pro marks on long and custom periods
ResultPaying users in several countries.
Three views and sharing

Different questions, one history

Different questions need different views of the same history. The calendar answers “where was I on that day”. Country cards show days per country for any period and open to the trips behind each total. The map shows the whole history at once.

Any country total or the map can be shared as a post or story card with the Expatly mark, so a personal milestone doubles as a small acquisition channel. Export covers practical needs: JSON as a backup that can be imported back, CSV for an accountant.

Calendar
Trips in one country
Map
Share card
←→
Release timeline

Grown in small releases

The product grew in small releases, each built on what the previous one recorded.

1
v1.0.0April 2025

Launch of the free tracker.

2
v1.0.2May 2025

Schengen calculator for planning trips and a Schengen summary on the home screen.

3
v1.1.0July 2026

Pro: photo and background check-ins, custom periods, export.

4
v1.2.0October 2026

Redesign for iOS 26, the map, imports from Google Maps Timeline and Flighty, widgets, a free photo-scan trial.

5
v1.3.0November 2026

Limits with official presets, a one-time Pro purchase as the default.

Outcome

Live, and growing

Apr 2025
Live on the App Store; five major releases since launch
Pro
Paying users in several countries since Pro launched in July 2026
5 languages
English, Spanish, Portuguese, Chinese and Russian, including the explanations of the rules
iOS 26
A design system for iOS 26 and Liquid Glass
Localization

One rule, five languages

The tax-residency preset in five languages: the rule, its source and what it doesn't cover follow the language of the app.

EN
ES
PT-BR
ZH
RU
←→
Reflection

What building a product alone taught me

The whole loop

Apart from engineering, I built Expatly from scratch: idea, research, pricing, interface, brand, translations, the App Store page. A designer in a team rarely sees the whole loop: an idea, a market, a release, a price, the first payments, the reviews, the next version. Each stage changes the one before it, and I now design with the whole loop in mind, not just the screen in front of me.

An owner's questions

When the product is yours, every decision is a bet with your own time and money. I stopped asking only how to design something and started asking whether it should exist, what it costs and how we will know it worked. That is the view I now bring to any team.

Every role's point of view

Being designer, product manager, marketer and owner at once taught me why each of these roles asks what it asks. Deadlines, pricing and scope stopped being obstacles and became part of the design problem, which makes me a better partner to the people I work with.

What the product taught me

Trust comes from correction, not accuracy

People accept automatic check-ins once they know they can fix them. The review screen did more for trust than any improvement to detection.

Rules are content, not just logic

Every preset carries an official source and a “checked on” date, so keeping them current is part of the product, not a one-off task.

Flexibility has a cost

Custom periods grew one option at a time until there were too many ways to set one up. Each option made sense alone; together they made a simple question hard to ask. Simplifying them is next.

Next case
From a costly third-party tool to an in-house messaging platform
Uspio · NDA · B2B · Web
1,000+
screens and states
Under NDA→