A clearer path to a new country.
Designing a personalized migration experience that turns fragmented administrative information into actionable, trustworthy guidance.
Moving to another country involves more than obtaining a visa. It means navigating unfamiliar systems, understanding administrative requirements, preparing documents, tracking deadlines, and making decisions that depend on individual circumstances.
For people moving from India to Germany, essential information is spread across embassy websites, government portals, universities, recognition authorities, and informal communities.
The challenge is not simply finding information.
It’s knowing which information applies to you, what to do with it, and when to act.
I designed Moveo to explore how a mobile experience could turn this fragmented process into a personalized, phase-aware journey while preserving access to authoritative sources.
Rather than asking users to interpret every requirement independently, Moveo brings planning, documents, timing, and contextual assistance into one experience.
Moveo uses migration context to organize relevant steps instead of presenting one generic checklist to everyone.
A phase-aware dashboard helps users focus on their current priorities without losing sight of what comes later.
Source transparency and explicit uncertainty states help users distinguish supported information from unresolved guidance.
Lia, Moveo’s AI assistant, is designed to explain and navigate information—not independently establish immigration requirements.
Migration information is distributed across institutions with different responsibilities. An embassy may explain visa procedures, a university may specify admission documents, and a local German authority may determine post-arrival administrative processes.
Each source can be useful within its own jurisdiction. But users must still connect the pieces.
This creates three interconnected challenges.
People repeatedly move between websites, messages, checklists, and personal notes to reconstruct the process.
Requirements may vary depending on migration purpose, educational background, application route, location, and timing.
Even when guidance appears understandable, users need to know whether it is authoritative, applicable, and current.
I wanted Moveo to reduce administrative effort while supporting informed decisions, rather than replacing one confusing information source with another.
Before defining the experience, I explored how people obtained information, organized their responsibilities, interpreted administrative requirements, and evaluated digital guidance.
The study combined exploratory research with later prototype evaluation.
Semi-structured interviews explored migration experiences and expectations.
The questionnaire examined information sources, administrative difficulty, planning methods, trust, AI expectations, and desired functionality.
The same five interview participants later evaluated the Moveo prototype through task-based scenarios.
| # | Finding | Evidence · of 18 respondents | Design opportunity |
|---|---|---|---|
| 01 | People were assembling their own information systemsRespondents combined official and informal sources; no single source provided everything. | 11/18 used government websites | Consolidate the journey without concealing where information originates. |
| 02 | Finding information didn’t mean understanding itNine of 18 met conflicting information and four were unsure. Deciding whether a requirement applied to them was the recurring difficulty. | 9/18 met conflicting information | Replace generic lists with context-sensitive guidance and explicit applicability. |
| 03 | Migration was experienced in phasesEight of 18 discovered at least one administrative task only after arriving in Germany. | 8/18 found a task only after arriving | Organize work into a temporal journey of current, upcoming and later actions. |
| 04 | People were already tracking everything manuallyTwelve used personal notes and eight used email reminders; seventeen used no dedicated app. | 12/18 used personal notes | Bring tasks, documents, timing and progress into one planning workspace. |
| 05 | Trust needed visible evidenceGovernment verification (14) and official source citations (10) mattered more than polish. | 14/18 wanted government verification | Make sources and uncertainty visible where users are deciding. |
| 06 | AI was useful, but not automatically trustedTen preferred AI explanations combined with official sources; eight preferred official sources alone. | 10/18 preferred AI plus official sources | Use AI as an optional explanatory layer within a source-first journey. |
I synthesized the research into four guiding needs.
Help users identify the requirements that apply to their own circumstances.
Make it clear where they are in the journey and what needs attention next.
Allow people to track progress, manage documents, and make decisions without unnecessary disclosure.
Keep consequential information traceable to an appropriate source.
These needs shaped the central product direction:
Use context and progressive disclosure to reduce the number of unrelated tasks users must evaluate.
Give immediate responsibilities visual priority while retaining access to the complete journey.
Make the basis of a task inspectable, including its source, applicability, and timing.
Allow users to make decisions, record progress, and choose whether to store sensitive documents.
When guidance is missing, conflicting, or unverified, communicate that limitation instead of generating a plausible answer.
Three personas guided the product decisions.
What each persona says, thinks, does and feels while preparing to move.
India to Germany migration, from planning to settling in.
The core design challenge was deciding how much information to show at once.
Displaying every possible migration requirement would create an overwhelming experience. Hiding too much could make users unsure whether the system had omitted something important.
I approached this through a layered information architecture:
Sets the context for every layer that follows.
The journey answers, “How does everything fit together?”
The dashboard answers, “What should I do next?”
The task detail answers, “What exactly is required?”
The source view answers, “Why should I trust this information?”
Each layer answers a different question.
I started with wireframes to settle structure before surface. Drag the slider to compare three of them with the final screens.
Migration requirements depend on context. Moveo’s onboarding experience is designed to capture the information needed to establish a relevant journey.
Instead of introducing a large administrative form, the experience progressively asks about migration purpose and other applicable circumstances.
The aim is to make personalization understandable and manageable rather than forcing users to interpret legal route terminology from the beginning.
Break complex profile collection into smaller decisions.
Present user-understandable choices while preserving the distinctions required for accurate pathway mapping.
Communicate how far users have progressed through setup.
Clarify why a question matters when it affects the resulting journey.
Use a short transition between onboarding steps. Selected options should respond immediately, while progress indicators advance consistently.
When setup finishes, transition from the selected migration context into the generated journey. The motion should communicate continuity: the answers the user just provided shape the plan they see next.
The dashboard brings the current migration stage, progress, and immediate actions together.
Rather than treating all tasks as equally important, Moveo emphasizes the next relevant action.
This approach reduces the effort required to interpret a long checklist while keeping the broader journey accessible.
Prioritize action over information volume.
The Next Step area serves as the main entry point into the user’s immediate responsibility.
Supporting sections provide progress, stage context, and upcoming work.
When a task is completed, the completion state should update immediately and the next relevant action should appear through a subtle content transition.
Avoid dramatic celebrations. Completing a migration task is often part of a longer administrative process, and the interface should reinforce clarity and progress rather than exaggerate success.
The migration plan translates the journey into individual tasks and supporting subtasks.
Each task needs to communicate what the user must do, what supporting documents may be needed, how the task relates to other work, and where its guidance comes from.
Breaking administrative work into smaller actions helps users understand what completion means.
A task can contain multiple preparatory activities, and its progress must reflect those activities reliably.
Not every task can be completed immediately. Some depend on other steps, personal circumstances, or external processes.
Moveo’s timing model aims to distinguish recommended preparation windows from actual authoritative deadlines.
This distinction became especially important during usability testing.
The document experience helps users identify and organize materials relevant to their journey.
However, the design deliberately separates three ideas:
A document may be required by an authority.
A user may have prepared that document.
A user may choose to store a copy in Moveo.
Preparing a document should not require uploading it into the app.
Use expandable subtasks with clear checked, unchecked, saving, and failed states.
Document cards should communicate preparation status independently of upload status.
For timing changes, animate the repositioning of affected tasks rather than abruptly replacing the entire timeline. If dates cannot be determined reliably, display an explicit verification state.
One of Moveo’s most important design decisions was treating information provenance as part of the user experience.
A requirement can be stored with a valid source in the backend and still be difficult to trust if the user cannot find that source.
Moveo’s design therefore emphasizes evidence access at the point where a task is interpreted.
Information grounded in the appropriate authoritative source and subject to verification.
Practical organization and recommendations that help users prepare, without being presented as legal obligations.
Advice and experiences from other migrants, which may provide context but do not establish universal requirements.
Keeping these categories separate prevents a useful personal suggestion from being mistaken for an official rule.
When source evidence is incomplete or conflicting, the experience should say so.
Instead of generating a confident task with unsupported requirements, Moveo is designed to preserve an unresolved state until the relevant information has been verified.
This was both an interaction design decision and a technical safety requirement.
Lia is Moveo’s AI assistant, designed to help users understand administrative information and navigate their journey.
I intentionally positioned Lia as contextual support rather than the primary structure of the application.
The research indicated that users wanted organized tasks and document checklists more consistently than AI explanations alone.
Use a consistent entry point for Lia throughout the application.
When opened from a task, the assistant should retain that task’s context. Responses should be visually structured, with a concise explanation followed by relevant source access where available.
Loading states should be restrained and should not imply that verification has occurred merely because the assistant has finished generating text.
Migration involves practical uncertainty beyond administrative rules.
People may want to locate relevant offices, understand local procedures, or connect with someone who has experienced a similar journey.
Moveo explores these needs through location-based discovery and community features.
Location-based tools help users discover relevant administrative services and understand where to go.
The concept connects people with similar migration contexts, providing an opportunity to exchange experiences and practical support.
Conversation creates space for reassurance and contextual knowledge that official instructions may not provide.
The design challenge is maintaining a clear boundary between personal experience and authoritative information.
A community member’s experience can be helpful without necessarily applying to another person’s situation.
Moveo’s interface carries a lot of serious information, so the design system had to make three things obvious at a glance: what is official, what needs action soon, and what comes from the AI guide.
Every value on this page is read from the Moveo Figma file: 81 colour tokens, 24 spacing values, 7 radii, motion durations and 14 text styles.
Blue is Moveo and official guidance. Indigo is reserved for Lia, so users can tell machine-generated help from verified requirements. Status colours always pair a strong tone with a pale surface and a dark text tone, so meaning never depends on colour alone.
#2563EB#1D4ED8#1E40AF#EFF6FF#BFDBFE#94C4FD#4F46E5#4338CA#3730A3#EEF2FF#E0E7FF#C7D2FE#16A34A#D97706#DC2626#0284C7#EA580C#F8FAFC#FFFFFF#F1F4F9#E2E8F0#64748B#0F172ABeyond brand and status, three token families name what something is, where the user is, and how soon it matters.
Inter at ten sizes, from the 32 px greeting down to the 10 px tab label. Semi Bold is used only for headings, so body copy stays quiet and readable.
Rounded corners from 4 to 24 px keep the interface approachable. Shadows are subtle, with one blue glow for the primary action and one focus ring that is always visible.
4812162024999924812162024324048648096Spacing scale in px · page gutter 20 · card padding 16 · section gap 24 · button height 56
Six core components cover most screens. Each has defined states, so the same card or field behaves the same way in the dashboard, the task flow and Lia.
A 24 px outline set with a 2 px stroke and round caps, so icons sit comfortably next to Inter and inherit the colour of their state.
Because meaning is encoded in tokens, a new screen can be built without inventing new colours.
I evaluated the Moveo prototype through five think-aloud sessions.
Participants worked through scenarios involving onboarding, migration pathway selection, dashboard navigation, tasks, document handling, timing, Lia, location search, and community interaction.
The evaluation examined both successful interactions and points of confusion.
Participants generally understood the value of bringing their migration responsibilities into one organized experience.
The dashboard, task structure, and overall consolidation were recurring sources of perceived usefulness.
The document interface was understandable, and community matching was seen as a potentially valuable form of practical support.
However, several issues revealed that clarity and trust could be undermined by relatively small interaction failures.
One participant encountered a recommendation displaying 2025 despite selecting a 2026 arrival context. Another questioned whether a displayed deadline was too early.
Dates in an administrative interface can be interpreted as authoritative instructions. An incorrect date is not merely a visual defect. It may influence real decisions.
Strengthen date derivation, distinguish planning recommendations from official deadlines, and prevent uncertain dates from appearing as confirmed guidance.
Some participants wanted source links directly beside the Next Step or task guidance. One participant responded positively when official sources were visible.
Source availability somewhere in the application was not sufficient. People needed evidence at the moment they were evaluating a requirement.
Bring source access closer to the task itself and provide deeper details through progressive disclosure.
A participant questioned whether uploading sensitive personal documents was necessary and expressed concern about potential misuse.
An easy upload flow does not mean users are comfortable disclosing sensitive information.
Separate document preparation from file storage and make uploading optional.
Two participants encountered subtasks that did not register as completed.
Completion affects progress, current-stage interpretation, and the next recommended action.
Provide immediate interaction feedback and ensure that dependent journey states update consistently.
Participants understood the potential value of contextual assistance, but raised concerns about chatbot authenticity, source quality, and inconsistent access. The evaluated Lia implementation was also incomplete.
Give Lia a stable entry point, clarify its supporting role, and prioritize source-grounded explanations.
Several participants encountered map-loading or office-search difficulties.
A loading failure could prevent the user from completing a practical administrative task.
Improve failure feedback, distinguish empty results from network errors, and provide recovery paths.
As Moveo developed, an important challenge emerged: a personalized interface can appear convincing even when the underlying information is incomplete.
This meant that the experience could not rely solely on well-designed screens or fluent AI explanations.
The system needed a way to distinguish verified requirements from proposed interpretations.
The implementation direction therefore separates several responsibilities.
Establishes where information originated.
Determine whether an extracted requirement is sufficiently supported.
Provides the controlled basis for applicable requirements.
Translates approved requirements into relevant tasks.
Helps prepare and explain information without becoming the authority that publishes it.
This separation supports the central UX principle of Moveo: a user should not receive an apparently authoritative instruction merely because an AI system can generate one.
The personalized journey engine and locally tested regulatory evidence-processing pipeline have been implemented in development.
However, the live authenticated regulatory publication process and fully verified production journey are not yet operational.
The research and usability evaluation supported Moveo’s central proposition: people valued having migration tasks, timing, documents, progress, and support organized within one coherent experience.
The strongest finding was not that users wanted more AI.
It was that they wanted less uncertainty about what to do next.
The evaluation also revealed an important tension. The more a user relies on a consolidated system, the more consequential its errors become.
A misleading deadline, missing requirement, or hidden source can undermine trust in the entire experience.
Designing a simple interface for a complex process requires carefully deciding what should be visible, what can be progressively disclosed, and what must never be hidden.
A source label is useful only if people can understand and inspect the evidence supporting their next decision.
In a consequential administrative context, the ability to communicate uncertainty is as important as the ability to generate an explanation.
Users need control over sensitive information at the moment they are asked to disclose it.
Even a clear, well-organized interface becomes less valuable when completion states, dates, or search results cannot be trusted.
The next priorities are to activate the verified regulatory information workflow, connect approved requirements to persistent personalized journeys, strengthen task and timeline reliability, and evaluate the refined experience with additional participants and migration contexts.
Future work will also examine more complete source-grounded Lia interactions, stronger location-search recovery, and broader pathway coverage.
The long-term vision is not to automate every migration decision.
It’s to give people a clearer, more trustworthy way to navigate the decisions they still need to make.
Closing statement
Moveo explores how thoughtful UX design, structured administrative planning, and accountable human–AI collaboration can make a complicated transition feel more understandable and manageable.