Mobile app development

Both, but native by default. Softwise builds native iOS apps in Swift and native Android apps in Kotlin, because that gives the most predictable performance and platform behaviour. A cross-platform build is recommended only when the product genuinely calls for it.

Yes. Store submission, review responses, and store metadata are included in the engagement. The team has released apps to both stores and handles rejections directly rather than passing them back to you.

It depends on scope, which is why scope and timeline are fixed in writing before development starts rather than estimated loosely and revised later. A focused first release is a different project from a multi-service platform: the super app Softwise built in Tunis carries shared identity, wallet, and chat underneath independent service verticals, which is a larger undertaking than a single-purpose app. The honest answer follows a scoping conversation rather than preceding one.

The same in-house team stays on it. Mobile apps need work after release regardless of build quality, because iOS and Android ship platform changes on their own schedule and store policies move without notice. Softwise engagements are structured as a build followed by ongoing support for that reason, so the people maintaining the app in year three are the ones who wrote it.

Yes. Inheriting existing code is normal work, and it starts by reading what is there rather than proposing a rewrite. Softwise migrated a recruitment SaaS platform in Dubai module by module with reversible cutovers instead of one risky switchover, and the same principle applies to a mobile codebase.