# App projects

> Explore 3 app project presentations from Webvelopment’s complete portfolio.

Canonical page: https://webvelopment.co.za/work/categories/app/

Language: en

Our work · App

Explore 3 app project presentations from Webvelopment’s complete portfolio.

## Project collection

[Browse the project categories](https://webvelopment.co.za/work/categories/)

[![Suzuki Secret Shopper — App portfolio cover](https://webvelopment.co.za/images/portfolio/1958.webp)

App

### Suzuki Secret Shopper](https://webvelopment.co.za/work/suzuki-secret-shopper/)[![Bonus Card — App portfolio cover](https://webvelopment.co.za/images/portfolio/1839.webp)

App

### Bonus Card](https://webvelopment.co.za/work/bonus-card/)[![Bonus App — App portfolio cover](https://webvelopment.co.za/images/portfolio/1836.webp)

App

### Bonus App](https://webvelopment.co.za/work/bonus-app/)

## Explore app presentations

Start with the task you want an app to make easier. As you browse, look at how each presentation groups information, draws attention to an action and helps someone find their way around. A screen can be a useful reference even when the project serves a different audience from yours.

This collection contains 3 projects in the original App category. Open a card to see its full available presentation and gallery, beyond the cover image. We have kept the names and category labels from the source collection so you can find and compare the same entries.

## Use the work to frame a useful discussion

Pick a screen that interests you and explain what you would borrow from it: perhaps the navigation, the amount of information shown at once or the prominence of the next action. Tell us what would need to change for your users, too. That gives us more to work with than a request for an app that simply looks similar.

The presentation alone does not establish device coverage, store distribution, offline behaviour or measured adoption. For your app, we will need to discuss target devices, account access, connectivity and who will handle ongoing updates.

## Plan the next step

Bring a project link and a short description of who will use your app, where they will use it and what they need to finish. If you have existing forms, content or screen sketches, include those along with any deadline and the person who will review the work. We can use those details to discuss discovery or a suitable delivery scope.

[Discuss an app brief](https://webvelopment.co.za/contact/) or [return to the complete portfolio](https://webvelopment.co.za/work/).

## Choose a task the app must complete

Choose one task and describe its beginning and end. For example, a staff member might open an unfinished form, add the missing information and submit it for review. What should they see to know it has been submitted? What should happen if their connection drops before they finish?

Use questions like these when comparing references. They help separate the visible screen layout from the behaviour your own app will need. If a recorded project’s background matters to your decision, ask us which details we can verify.

[Explore the relevant service](https://webvelopment.co.za/services/development/app-development/) · [Compare the complete project archive](https://webvelopment.co.za/work/) · [Discuss this kind of project](https://webvelopment.co.za/contact/).

Let’s move things forward

## Start a conversation

Tell us what you are working towards. We’ll help you find a practical next step.

[Let’s talk](https://webvelopment.co.za/contact/)