← All work
Native Design System
One foundation. Three apps.
A design system for three native iOS and Android apps, built from zero.
My role
Proposed the approach; set the foundation
Team
Me + 1 designer
Platform
Native iOS and Android
Timeframe
2025 — ongoing
9:41
Good morning, Sam
My properties
This month
This year
Occupancy
78%
Earnings
$12,480
Upcoming stays
Lakeview Cottage
Oct 12 – 15 · 3 nights
Confirmed
Harbor Loft
Oct 16 – 21 · 5 nights
Confirmed
Pine Suite
Oct 22 – 24 · 2 nights
Pending
Home
Calendar
Statements
Profile
Owner app
Native app A
9:41
Seaside Loft
Oct 12 – 15 · 2 guests
Confirmed
Check-in in 2 days
Check-in
From 4:00 PM
›
Wi-Fi
Network and password
›
House guide
Parking, trash, quiet hours
›
Get directions
Trip
Explore
Messages
Profile
Guest app
Native app B
9:41
Tuesday, Oct 14
Today’s cleans
5 of 8 done
3 left
All
To do
Done
Harbor Loft
Checkout clean · 10:00
MR
Pine Suite
Inspection · 11:30
JT
✓
Cedar Cabin
Checkout clean · 9:00
AL
Today
Schedule
Team
Profile
Housekeeping app
Native app C
Visuals are original illustrations created for this portfolio and do not depict proprietary product screens.
A second system, on purpose.
The web design system is responsive and built for the browser. The company’s three native apps, built for owners, guests, and housekeeping teams, needed components designed for iOS and Android. Their web versions stay on the web system. The native apps got a foundation of their own, designed with the apps’ cross-platform framework in mind, so one component set serves both platforms.
One library. Three products.
Instead of a separate library for each app, I proposed one: a single foundation and component set, with each app distinguished by its product color.
Default
Pressed
Disabled
Native app A
Continue
Continue
Continue
Native app B
Continue
Continue
Continue
Native app C
Continue
Continue
Continue
Same component, same states, three product colors.
Aa
Theme
One product color per app
Components
One shared set for all three apps
Foundation
Inter, 16px base, numeric tokens
16px
Inter as the base type size
radius-6 · 8
Numeric, value-based tokens
3 states
Default, pressed, and disabled
2 modes
Light and dark, for every app
A foundation built for native.
I defined the foundation first, with tokens for all three apps created at once, in both light and dark mode. Components are added as the apps need them, so the foundation is what keeps them consistent as the system grows.
Aa
Inter
16px base size
radius
-
8
What it measures
Its value, in pixels
radius-6
6px corners
radius-8
8px corners
Shown enlarged for clarity
9:41
Good morning, Sam
My properties
This month
This year
Occupancy
78%
Earnings
$12,480
Upcoming stays
Lakeview Cottage
Oct 12 – 15 · 3 nights
Confirmed
Harbor Loft
Oct 16 – 21 · 5 nights
Confirmed
Pine Suite
Oct 22 – 24 · 2 nights
Pending
Home
Calendar
Statements
Profile
Light
9:41
Good morning, Sam
My properties
This month
This year
Occupancy
78%
Earnings
$12,480
Upcoming stays
Lakeview Cottage
Oct 12 – 15 · 3 nights
Confirmed
Harbor Loft
Oct 16 – 21 · 5 nights
Confirmed
Pine Suite
Oct 22 – 24 · 2 nights
Pending
Home
Calendar
Statements
Profile
Dark
Tokens for every app, in light and dark mode.
Set the foundation. Handed off the growth.
I proposed the approach and established the foundation and direction. Then I handed a designer on my team ownership of expanding the component set, because I wanted her to own meaningful work. I set the strategy; she built on it.
First screens shipped. Clients noticed.
The first app is fully designed on the shared foundation, and its dashboard and first redesigned screens have shipped. Clients responded very positively to how they look, the information they show, and how they work. The other apps will reuse the same components instead of starting over.
The web system and the native system share a rule, not a library: standardize what’s solved, design what’s specific.
Next case study
Unified Inbox →
Product design leader. Design functions,
systems, and products for complex SaaS.
Work
Web design system
Native design system
Unified Inbox
AI capability
About
About
Résumé
© 2026 Alina Dohotaru
Visuals are original illustrations and do not depict proprietary product screens.
← All work
Native Design System
One foundation. Three apps.
A design system for three native iOS and Android apps, built from zero.
My role
Proposed the approach; set the foundation
Team
Me + 1 designer
Platform
Native iOS and Android
Timeframe
2025 — ongoing
9:41
Good morning, Sam
My properties
This month
This year
Occupancy
78%
Earnings
$12,480
Upcoming stays
Lakeview Cottage
Oct 12 – 15 · 3 nights
Confirmed
Harbor Loft
Oct 16 – 21 · 5 nights
Confirmed
Pine Suite
Oct 22 – 24 · 2 nights
Pending
Home
Calendar
Statements
Profile
Owner app
Native app A
9:41
Seaside Loft
Oct 12 – 15 · 2 guests
Confirmed
Check-in in 2 days
Check-in
From 4:00 PM
›
Wi-Fi
Network and password
›
House guide
Parking, trash, quiet hours
›
Get directions
Trip
Explore
Messages
Profile
Guest app
Native app B
9:41
Tuesday, Oct 14
Today’s cleans
5 of 8 done
3 left
All
To do
Done
Harbor Loft
Checkout clean · 10:00
MR
Pine Suite
Inspection · 11:30
JT
✓
Cedar Cabin
Checkout clean · 9:00
AL
Today
Schedule
Team
Profile
Housekeeping app
Native app C
Visuals are original illustrations created for this portfolio and do not depict proprietary product screens.
A second system, on purpose.
The web design system is responsive and built for the browser. The company’s three native apps, built for owners, guests, and housekeeping teams, needed components designed for iOS and Android. Their web versions stay on the web system. The native apps got a foundation of their own, designed with the apps’ cross-platform framework in mind, so one component set serves both platforms.
One library. Three products.
Instead of a separate library for each app, I proposed one: a single foundation and component set, with each app distinguished by its product color.
Default
Pressed
Disabled
Native app A
Continue
Continue
Continue
Native app B
Continue
Continue
Continue
Native app C
Continue
Continue
Continue
Same component, same states, three product colors.
Aa
Theme
One product color per app
Components
One shared set for all three apps
Foundation
Inter, 16px base, numeric tokens
16px
Inter as the base type size
radius-6 · 8
Numeric, value-based tokens
3 states
Default, pressed, and disabled
2 modes
Light and dark, for every app
A foundation built for native.
I defined the foundation first, with tokens for all three apps created at once, in both light and dark mode. Components are added as the apps need them, so the foundation is what keeps them consistent as the system grows.
Aa
Inter
16px base size
radius
-
8
What it measures
Its value, in pixels
radius-6
6px corners
radius-8
8px corners
Shown enlarged for clarity
9:41
Good morning, Sam
My properties
This month
This year
Occupancy
78%
Earnings
$12,480
Upcoming stays
Lakeview Cottage
Oct 12 – 15 · 3 nights
Confirmed
Harbor Loft
Oct 16 – 21 · 5 nights
Confirmed
Pine Suite
Oct 22 – 24 · 2 nights
Pending
Home
Calendar
Statements
Profile
Light
9:41
Good morning, Sam
My properties
This month
This year
Occupancy
78%
Earnings
$12,480
Upcoming stays
Lakeview Cottage
Oct 12 – 15 · 3 nights
Confirmed
Harbor Loft
Oct 16 – 21 · 5 nights
Confirmed
Pine Suite
Oct 22 – 24 · 2 nights
Pending
Home
Calendar
Statements
Profile
Dark
Tokens for every app, in light and dark mode.
Set the foundation. Handed off the growth.
I proposed the approach and established the foundation and direction. Then I handed a designer on my team ownership of expanding the component set, because I wanted her to own meaningful work. I set the strategy; she built on it.
First screens shipped. Clients noticed.
The first app is fully designed on the shared foundation, and its dashboard and first redesigned screens have shipped. Clients responded very positively to how they look, the information they show, and how they work. The other apps will reuse the same components instead of starting over.
The web system and the native system share a rule, not a library: standardize what’s solved, design what’s specific.
Next case study
Unified Inbox →
Product design leader. Design functions,
systems, and products for complex SaaS.
Work
Web design system
Native design system
Unified Inbox
AI capability
About
About
Résumé
© 2026 Alina Dohotaru
Visuals are original illustrations and do not depict proprietary product screens.
Alina Dohotaru
Home
Work
About
Résumé
Contact
← All work
Native Design System
One foundation. Three apps.
A design system for three native iOS and Android apps, built from zero.
My role
Proposed the approach; set the foundation
Team
Me + 1 designer
Platform
Native iOS and Android
Timeframe
2025 — ongoing
9:41
Good morning, Sam
My properties
This month
This year
Occupancy
78%
Earnings
$12,480
Upcoming stays
Lakeview Cottage
Oct 12 – 15 · 3 nights
Confirmed
Harbor Loft
Oct 16 – 21 · 5 nights
Confirmed
Pine Suite
Oct 22 – 24 · 2 nights
Pending
Home
Calendar
Statements
Profile
Owner app
Native app A
9:41
Seaside Loft
Oct 12 – 15 · 2 guests
Confirmed
Check-in in 2 days
Check-in
From 4:00 PM
›
Wi-Fi
Network and password
›
House guide
Parking, trash, quiet hours
›
Get directions
Trip
Explore
Messages
Profile
Guest app
Native app B
9:41
Tuesday, Oct 14
Today’s cleans
5 of 8 done
3 left
All
To do
Done
Harbor Loft
Checkout clean · 10:00
MR
Pine Suite
Inspection · 11:30
JT
✓
Cedar Cabin
Checkout clean · 9:00
AL
Today
Schedule
Team
Profile
Housekeeping app
Native app C
Visuals are original illustrations created for this portfolio and do not depict proprietary product screens.
A second system, on purpose.
The web design system is responsive and built for the browser. The company’s three native apps, built for owners, guests, and housekeeping teams, needed components designed for iOS and Android. Their web versions stay on the web system. The native apps got a foundation of their own, designed with the apps’ cross-platform framework in mind, so one component set serves both platforms.
One library. Three products.
Instead of a separate library for each app, I proposed one: a single foundation and component set, with each app distinguished by its product color.
Default
Pressed
Disabled
Native app A
Continue
Continue
Continue
Native app B
Continue
Continue
Continue
Native app C
Continue
Continue
Continue
Same component, same states, three product colors.
Aa
Theme
One product color per app
Components
One shared set for all three apps
Foundation
Inter, 16px base, numeric tokens
16px
Inter as the base type size
radius-6 · 8
Numeric, value-based tokens
3 states
Default, pressed, and disabled
2 modes
Light and dark, for every app
A foundation built for native.
I defined the foundation first, with tokens for all three apps created at once, in both light and dark mode. Components are added as the apps need them, so the foundation is what keeps them consistent as the system grows.
Aa
Inter
16px base size
radius
-
8
What it measures
Its value, in pixels
radius-6
6px corners
radius-8
8px corners
Shown enlarged for clarity
9:41
Good morning, Sam
My properties
This month
This year
Occupancy
78%
Earnings
$12,480
Upcoming stays
Lakeview Cottage
Oct 12 – 15 · 3 nights
Confirmed
Harbor Loft
Oct 16 – 21 · 5 nights
Confirmed
Pine Suite
Oct 22 – 24 · 2 nights
Pending
Home
Calendar
Statements
Profile
Light
9:41
Good morning, Sam
My properties
This month
This year
Occupancy
78%
Earnings
$12,480
Upcoming stays
Lakeview Cottage
Oct 12 – 15 · 3 nights
Confirmed
Harbor Loft
Oct 16 – 21 · 5 nights
Confirmed
Pine Suite
Oct 22 – 24 · 2 nights
Pending
Home
Calendar
Statements
Profile
Dark
Tokens for every app, in light and dark mode.
Set the foundation. Handed off the growth.
I proposed the approach and established the foundation and direction. Then I handed a designer on my team ownership of expanding the component set, because I wanted her to own meaningful work. I set the strategy; she built on it.
First screens shipped. Clients noticed.
The first app is fully designed on the shared foundation, and its dashboard and first redesigned screens have shipped. Clients responded very positively to how they look, the information they show, and how they work. The other apps will reuse the same components instead of starting over.
The web system and the native system share a rule, not a library: standardize what’s solved, design what’s specific.
Next case study
Unified Inbox →
Product design leader. Design functions,
systems, and products for complex SaaS.
Work
Web design system
Native design system
Unified Inbox
AI capability
About
About
Résumé
Contact
aln.dohotaru@gmail.com
© 2026 Alina Dohotaru
Visuals are original illustrations and do not depict proprietary product screens.
← All work
Native Design System
One foundation. Three apps.
A design system for three native iOS and Android apps, built from zero.
My role
Proposed the approach; set the foundation
Team
Me + 1 designer
Platform
Native iOS and Android
Timeframe
2025 — ongoing
9:41
Good morning, Sam
My properties
This month
This year
Occupancy
78%
Earnings
$12,480
Upcoming stays
Lakeview Cottage
Oct 12 – 15 · 3 nights
Confirmed
Harbor Loft
Oct 16 – 21 · 5 nights
Confirmed
Pine Suite
Oct 22 – 24 · 2 nights
Pending
Home
Calendar
Statements
Profile
Owner app
Native app A
9:41
Seaside Loft
Oct 12 – 15 · 2 guests
Confirmed
Check-in in 2 days
Check-in
From 4:00 PM
›
Wi-Fi
Network and password
›
House guide
Parking, trash, quiet hours
›
Get directions
Trip
Explore
Messages
Profile
Guest app
Native app B
9:41
Tuesday, Oct 14
Today’s cleans
5 of 8 done
3 left
All
To do
Done
Harbor Loft
Checkout clean · 10:00
MR
Pine Suite
Inspection · 11:30
JT
✓
Cedar Cabin
Checkout clean · 9:00
AL
Today
Schedule
Team
Profile
Housekeeping app
Native app C
Visuals are original illustrations created for this portfolio and do not depict proprietary product screens.
A second system, on purpose.
The web design system is responsive and built for the browser. The company’s three native apps, built for owners, guests, and housekeeping teams, needed components designed for iOS and Android. Their web versions stay on the web system. The native apps got a foundation of their own, designed with the apps’ cross-platform framework in mind, so one component set serves both platforms.
One library. Three products.
Instead of a separate library for each app, I proposed one: a single foundation and component set, with each app distinguished by its product color.
Default
Pressed
Disabled
Native app A
Continue
Continue
Continue
Native app B
Continue
Continue
Continue
Native app C
Continue
Continue
Continue
Same component, same states, three product colors.
Aa
Theme
One product color per app
Components
One shared set for all three apps
Foundation
Inter, 16px base, numeric tokens
16px
Inter as the base type size
radius-6 · 8
Numeric, value-based tokens
3 states
Default, pressed, and disabled
2 modes
Light and dark, for every app
A foundation built for native.
I defined the foundation first, with tokens for all three apps created at once, in both light and dark mode. Components are added as the apps need them, so the foundation is what keeps them consistent as the system grows.
Aa
Inter
16px base size
radius
-
8
What it measures
Its value, in pixels
radius-6
6px corners
radius-8
8px corners
Shown enlarged for clarity
9:41
Good morning, Sam
My properties
This month
This year
Occupancy
78%
Earnings
$12,480
Upcoming stays
Lakeview Cottage
Oct 12 – 15 · 3 nights
Confirmed
Harbor Loft
Oct 16 – 21 · 5 nights
Confirmed
Pine Suite
Oct 22 – 24 · 2 nights
Pending
Home
Calendar
Statements
Profile
Light
9:41
Good morning, Sam
My properties
This month
This year
Occupancy
78%
Earnings
$12,480
Upcoming stays
Lakeview Cottage
Oct 12 – 15 · 3 nights
Confirmed
Harbor Loft
Oct 16 – 21 · 5 nights
Confirmed
Pine Suite
Oct 22 – 24 · 2 nights
Pending
Home
Calendar
Statements
Profile
Dark
Tokens for every app, in light and dark mode.
Set the foundation. Handed off the growth.
I proposed the approach and established the foundation and direction. Then I handed a designer on my team ownership of expanding the component set, because I wanted her to own meaningful work. I set the strategy; she built on it.
First screens shipped. Clients noticed.
The first app is fully designed on the shared foundation, and its dashboard and first redesigned screens have shipped. Clients responded very positively to how they look, the information they show, and how they work. The other apps will reuse the same components instead of starting over.
The web system and the native system share a rule, not a library: standardize what’s solved, design what’s specific.
Next case study
Unified Inbox →
Product design leader. Design functions,
systems, and products for complex SaaS.
Work
Web design system
Native design system
Unified Inbox
AI capability
About
About
Résumé
© 2026 Alina Dohotaru
Visuals are original illustrations and do not depict proprietary product screens.