# Teacherspace / Loading
ScreensLoading
Waiting that doesn’t feel like waiting
Skeleton screens that show the shape of the answer while the AI is still working.
View on DribbbleThe work
The moments we design
Every screen has more than one version. We design all of them, not just the ideal one.
- Empty states and first use
- Loading and skeleton screens
- Error messages and recovery
- Success and confirmation
- Offline and slow connections
- Long names, missing data and edge cases
- Locked features and upgrade prompts
- Form validation
- Copy for errors and empty states
- Transitions between states
- State components in your library
- AI waiting and failure states
The problem
Sounds familiar?
If 2 or more of these ring true, the gaps are in the states, not the main screens.
{{ countLabel }}
{{ ctaText }}Book a call
Selected work
Selected sub-cases work
Screens on Dribbble and Behance
# Revisual / Sync error
ScreensError
When sync fails, say what happened
A calendars table that flags the failed sync, explains why and links to the fix.
View on Dribbble# Influencer Marketing AI / Transactions
ScreensSuccess
Confirmation people can trust
Each step confirms the transaction link was created, with the next action right there.
View on Dribbble# Replicate Labs / Learning path
ScreensProgress
Done, retake or still ahead
A learning path where every step shows its state: completed, scored with a retake option, or still to come, with a clear pass threshold for each.
View on BehanceProof
“I’ve had the pleasure of working with Sevgi and her team across multiple projects, and in every case, they’ve been both highly creative and professional.”
- Upwork Job Success
- 100%
- Regular clients
- 10+
- Recognized by
- Dribbble Select
Ways to start
2 ways to start
Design the states for new features, or audit the product you already have.
-
# New features
Design the missing states
Map every state for your key flows before developers start building.
- State inventory for key flows
- Empty, loading, error and success designs
- Copy for every state
- Dev-ready handoff in Figma
-
# Live product
Audit your live product
Find the screens that break when things aren’t perfect, then fix them.
- Edge-case review of the live product
- Prioritized findings
- Redesigned states
- Dev-ready handoff in Figma
01What counts as a state?
Anything that isn’t the ideal screen: empty, loading, error, success, offline, locked, partial and first-use views.
02How long does a project take?
It depends on the scope. Once we’ve seen the full picture, we’ll share a rough timeline.
03Can you add states to designs we already have?
Yes. We work from your Figma files or the live product and fill in what’s missing.
04Do you write the copy too?
Yes. Error and empty-state copy is part of the work, so every state says what happened and what to do next.
05Do you build the screens?
No. We’re a design studio. You get designs and handoff files your developers build from, and we stay on hand during the build.
