The MealDBDessertRecipesApp is a mobile application that provides a collection of dessert recipes for users to explore and try out. It offers a variety of dessert options and allows users to view detailed information about each recipe.



  • Browse a list of dessert recipes.
  • View detailed information about a specific recipe
  • Recipes sorted alphabetically

Screenshots from TheMealDBDessertRecipesApp:

Simulator Screenshot - iPhone 14 Pro - 2023-06-16 at 02 00 55 Simulator Screenshot - iPhone 14 Pro - 2023-06-16 at 02 01 14

(Screen Recording of App:

MVVM Architecture:

The app follows the MVVM architectural pattern, which separates the user interface (View) from the underlying data (Model) by introducing a mediator component called ViewModel. Here’s how the components are organized in the app:



  • Rendering the user interface and handling user interactions
  • DessertListView: Rendering the list of desserts
  • DessertDetailView: Rendering the details of a selected dessert


  • Acts as a bridge between the View and the Model
  • Retrieves the necessary data from the Model and prepares it for presentation in the View
  • DessertListViewModel: Responsible for fetching the dessert list from the API and managing the list of desserts. It holds an instance of DessertDetailViewModel to handle the details of the selected dessert. It provides methods for populating the dessert list, selecting a dessert, and updating the state of the selected dessert
  • DessertDetailViewModel: Handles the fetching and presentation of the details for a selected dessert


  • DessertListScreen: Brings together multiple views (DessertListView + DessertDetailView)

The MVVM architecture helps to maintain a clear separation of concerns, making the code more modular and testable. It enables easier maintenance and extensibility as the application grows.

Unit Testing

  • The unit testing suite focuses on testing the various components of the app, including:

Model: Tests the data structures ain the model layer. This includes testing decoding of JSON responses and data transformations.

ViewModel: ViewModel tests verify that the ViewModel properly handles data retrieval, transformation

  • Unit testing was done following dependency injection to allow for easier testing by “injecting” mock dependencies. I created the MockWebservice class to help implement this. It simulates the behavior of the actual web service by providing mock responses from JSON data files. The mock data responses are stored as JSON files within the project’s test bundle.

  • The JSON data files contain sample responses that represent various scenarios and edge cases that need to be tested. Each JSON file corresponds to a specific API endpoint or data structure used in the app. The test cases can load the mock data from these files and use them to simulate network requests and responses.

  • The Mocks folder contains the Mock Webservice, mock data responses, and a loadMockData method to load the data responses from the JSON files.

  • A design decision was made to not unit test the Views in isolation, because of their dependency on the underlying framework. The Views could be tested down the line with integration tests.


View Github