UX UI design
Website and app UX UI design tested before development
Website and app UX UI design organises user flows and screen layouts before development. The agreed deliverables may include a Figma design, interactive prototype and files for developers.
Website and app UX UI design: what the service covers
Changing a button in a design takes minutes. Changing it after coding takes days and may break something else. So at PROIDEA Egypt we hold to a rule: no code until you approve the design on desktop and mobile. In apps and systems, where screens are many and paths tangled, an interactive prototype saves weeks of rebuilding.
A good interface also means a user who finishes the task without asking anyone: a staff member logs an order in half the time, a customer books without phoning you.
UX and UI: the difference
UX (user experience) is the path: what a person does to reach a goal, how many steps, where they stumble and what they see at each one. UI (user interface) is the look: colours, fonts, buttons, icons and spacing. You start with the path, then dress it.
How we work
1. Understanding
Who uses the screen? A warehouse worker wearing gloves or a woman on a phone with one hand? What do they want to get done? We read any old system or live site you have and ask real users to describe what annoys them.
2. Flows and structure
We draw the user's trip from first opening to finished task, decide the screens needed and what each shows, and map the navigation. We cut steps to the minimum, because every extra screen loses some users.
3. Wireframes
Simple black-and-white sketches that arrange elements with no colour. You discuss them with us and change them in minutes, and agree the structure before looks take over.
4. Final design
In Figma we design every screen in your identity and in its different states: empty, loading, error and success. That covers mobile, tablet and desktop where needed.
5. A design system
We gather repeating parts in a library: colours, fonts, buttons, fields, cards and messages. That keeps later screens consistent without rebuilding from nothing, and speeds up the developer.
6. The interactive prototype
We link the screens so a tap on a button leads to the next screen, as if you were using the app. You open it on your phone with your team, and perhaps with some customers, and find problems before coding.
7. Developer handover
Organised files with sizes, colours, fonts, images and icons, and a description of behaviour: what happens on tap, what the screen shows on error. Handed to our team or to any team you choose.
What is special about Arabic interfaces
- Right-to-left direction. Flipping the screen is not enough. Directional icons (arrows, progress, back) mirror, while some elements such as numbers, clocks and logos do not.
- Fonts. Arabic fonts readable on small screens in several weights, matched with Latin when the two languages mix.
- Long text. Arabic takes space differently from English, so we check that buttons and headings do not break.
- Numbers and dates. We agree with you which forms show: Arabic-Indic or Western digits, Hijri or Gregorian.
- Two languages in one interface. Switching language without the user losing their place.
Mobile apps and dashboards
App design differs from website design: the thumb is the controller, the screen is small and the connection may drop. We respect the thumb zone, button size and offline states. An admin dashboard differs too: dense data, tables, filters and quick actions. See mobile app development and custom software.
Websites and stores
Design for a WordPress site or a store can begin with a Figma prototype your team approves before building. This is how we run website projects: the design is approved on desktop and mobile before coding. See company website design, landing pages and store conversion.
Identity and interface
The interface wears your identity. If you have none, we suggest designing it first so screens are not built on temporary colours.
Project steps
- A call. The product, the user and what does not work now.
- A written quote that sets the scope and timeline.
- Flows and wireframes that you approve.
- Final design for desktop and mobile.
- The interactive prototype, trial and recorded notes.
- Handover with Figma files, the design system and behaviour notes.
What we need from you
A description of the product, examples of apps or sites you like, your identity, access to real users to test with if possible, and someone who makes design decisions.
What you receive
An organised Figma file, a design system, an interactive prototype, a flow diagram, developer handover files, and a short walkthrough on reading them.
Packages and the written quote
We review what you need, then send a written quote that sets the scope, timeline and deliverables. The written quote fixes the scope and the timeline, and we start after you approve it. Design is part of our mobile app and website packages, or you can order it alone.
Frequently asked questions
Yes. We hand you files to give to any development team, and we write the behaviour notes for them.
The count is set in the quote according to the product. A simple app runs to dozens of screens and an admin system to more. We list them with you at the flows stage.
We trial the prototype with your team, and with users you point us to where possible. The package defines the testing.
Ownership terms and the licensing of fonts and images are written into the quote before work begins.
In either or both, with a language switch inside the prototype.
Try your app on your phone before it is coded
Send the product requirements and intended users and who will use it, and we reply with a written quote that sets the scope and timeline.