Software engineering · Kosovo
A mobile product needs more than a collection of screens. People must be able to start a task, understand its status and recover when something interrupts it. PREJ develops Android and iOS applications with React Native and Expo, connecting the mobile experience to the APIs and operational tools behind it. We begin with the people using the product and the real conditions in which they will use it.
Discuss your project ↗What we can build together
Booking a service, following an assignment or checking a status each involves different decisions. We map the important states before implementation: the first visit, an action in progress, a changed request and a completed task. That makes the scope easier to review and gives the interface a clear purpose. Permissions, account roles and the information visible to each user belong in that discussion, not as an afterthought.
Where the product calls for them, mobile work can include maps, location, notifications and backend integration. We define which information the app reads, which actions change it and how the administrative workspace stays in step. An interface should not promise that an action succeeded before the system has confirmed it. Network interruptions and rejected requests need understandable responses and a way to continue.
A useful pilot answers specific questions with a limited audience. A store release adds a separate set of requirements, device checks and publishing steps. We agree which platforms and flows belong to each stage rather than treating an Android build as proof of an iOS release. Hosting, external services, app-store accounts and ongoing support are discussed explicitly for the particular project.
We first clarify the problem and the smallest useful product. We then work through interfaces and implementation in reviewable increments, checking the complete journey rather than isolated screens. The handover makes known limitations visible, so the next decision is based on evidence. You work directly with Xhevdet Ferizi on the technical direction; AI tools assist the engineering workflow, while decisions and accountability remain human.
Related development work
PREJ TaxiApp connects dedicated rider and driver apps with dispatch oversight and administration. Its booking, location, trip-status and cash-fare workflows illustrate why the mobile interface and backend must be designed together. The current portfolio describes Android pilot builds and documented ride-flow testing. Public commercial rollout and iOS release remain separate delivery stages; this is development evidence, not a claim of a live commercial fleet.
Explore this project and its current stage ↗We start by reviewing its available interfaces, authentication, data model and limitations. Integration scope depends on what the existing system supports. If changes are needed, they should be agreed before the mobile app relies on them.
A short explanation of the users and their main task is enough to start. Existing screens, systems, platform preferences and operational constraints help us turn that conversation into a realistic first scope.
Tell us who will use the product, what they need to do and which systems already exist. We will discuss the scope, constraints and next useful step.
Discuss your project ↗