SeenTK

Mobile app development in Syria

Mobile app development in Syria, from idea to a usable product

Based in Damascus, SeenTK develops mobile products for founders and businesses. We define the user experience, first release, admin tools, and integrations before design, development, testing, and store preparation. Damanak and VoiceBrief are two examples you can explore before discussing your app.

Damanak: warranties and after-sales workflows

We developed Damanak to organise product and customer records, issue digital warranty cards, scan barcodes or serial numbers, and track claims and store-team permissions. It demonstrates how connected operational tasks can become a business app. Review the implementation scope and screens in the case study, or explore the public App Store listing.

VoiceBrief: audio turned into reviewable next steps

We developed VoiceBrief to turn user-selected audio into a transcript, summary, key points, action items, and reviewable dates. The product connects audio selection, processing, and a structured result in one workflow. AI-generated words and dates still need user review; the output is not a substitute for checking important details.

Define what the first release should do

Start with a complete core workflow, such as creating and tracking an order, booking a service, or managing a customer record. We identify roles, screens, notifications, and data. An admin dashboard is included when operations require it; secondary features can wait until the initial idea has been tested.

Choosing an approach for iOS and Android

Devices, integrations, and budget guide the technology choice. Flutter can suit a shared codebase across both systems, while platform-specific features may need native development or additional integrations. Support for both platforms and offline use must be agreed in the scope, not assumed.

Design, testing, and store preparation

After requirements and user flows, we approve screen designs when needed, develop the product, and test the main journeys and error states on agreed devices. We review Arabic reading direction, screen sizes, and weak connectivity. Store files and publishing materials are prepared according to scope; review timing and acceptance remain with the store.

What determines app development cost?

User roles, workflows, administration, integrations, subscriptions, and offline requirements matter more than screen count alone. Share the main use case, target devices, and any existing design or system so a realistic first stage can be estimated. Developer accounts, hosting, external services, and support are clarified in the proposal.

Useful SeenTK links

Common questions

Can we start with only an idea?

Yes. Describe the problem, audience, and core action; we can turn them into an initial scope and screens before estimating development.

Can I see published examples?

Yes. Damanak and VoiceBrief have public App Store listings and case studies with screenshots. Publication does not guarantee that an app is error-free.

Does every app need an admin dashboard?

No. It depends on how content, orders, and accounts are managed. We separate in-app functions from any independent management interface.

Do you guarantee store approval?

We prepare the product and submission materials within the agreed scope and store requirements. Apple or Google makes the review and approval decision.