Workflows and statuses
We describe inputs, steps and possible exceptions. Overviews, search and status indicators are planned around the decisions people need to make during their work.
03 / 04Services
Web application development for a clearer working day.
Information getting lost between spreadsheets and messages? I build web applications that bring agreed tasks together in the browser and help everyone involved understand what needs to happen next.
Mojtaba Jafari in Wolfsburg, Germany · Remote collaboration in German, English and Persian.
Web applications
For recurring tasks involving several people
Customer portal, appointment tool or internal dashboard: we start with one real example. Who begins the process, what information do they need, and when is the task complete?
Web applications
What we can plan together
Roles and permissions
Who can view, edit or approve information? We define user groups and access rights, including sign-in and account management within the agreed scope.
Data and integrations
We check existing data sources and the connections you need. Access, exchange formats and what happens when a transfer fails are part of that planning.
Operation and upkeep
Data protection requirements, backups and responsibilities are discussed early. We agree which operational and maintenance tasks are included before development and handover.
Fictional design concept
Ideas to explore and try
Fictional design concepts with sample content. These are not client projects, released products or real offers.
Web applications
How your project takes shape
- 01
Walk through a real task
A concrete example identifies people, data and exceptions, helping us define a focused first version.
- 02
Agree how it will work
You review designs against your daily work. I then implement the agreed workflows and connections.
- 03
Test tasks and permissions
We check tasks and selected failure cases. Handover covers accounts, everyday use and operational responsibilities.
Questions before getting started
Can you connect the system I already use?
That depends on its available interfaces, access permissions and contractual terms. We examine the specific connection before including it in the agreed scope.
Does every user need the same features?
No. We can plan different roles, such as customer and administrator. The screens and actions available to each role follow your actual processes.
Can we start with just one workflow?
Yes. A clearly bounded first version makes requirements and feedback easier to assess. Later additions can be planned with existing data and working practices in mind.
Web applications
Which process needs a clearer overview?
Describe a recurring task and the people involved. We can work out which application would help and define its first version.