Scribd
Upload
10 views

iOS Developer Challenge

This document outlines specifications for an event application, including a splash screen, events screen with tabs for different categories, and an event details screen. It provides details on functionality for each screen and notes that source code should be delivered using clean architecture principles, design patterns like MVP or MVVM, and unit tests with progressive code commits. Web services are specified for getting event types and listing events with pagination. Wireframes are also referenced.

Uploaded by

gung
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
10 views

iOS Developer Challenge

This document outlines specifications for an event application, including a splash screen, events screen with tabs for different categories, and an event details screen. It provides details on functionality for each screen and notes that source code should be delivered using clean architecture principles, design patterns like MVP or MVVM, and unit tests with progressive code commits. Web services are specified for getting event types and listing events with pagination. Wireframes are also referenced.

Uploaded by

gung
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

iOS Developer Challenge

OVERVIEW
Implement a simple Event Application.

SPECIFICATIONS
Splash Screen
1. A simple screen that will be launched every time the user opens the app.

Events Screen
1. The Events Screen should contain tabs that represent the different event category types. For example the
rst tab could represent the "Entertainment" category and all events in this tab should belong to the
"Entertainment" category, and so on

2. Every tab should load only after it is clicked, not before

3. Every tab should have a list of card views that contain a brief overview of the event. (i.e name, location,
image, start and end dates)

4. The list should support pull to refresh and in nite loading functionality.

Event Details Screen


1. Displays all the data of the event which is event name, image, date, description and map that has the
location of the event.
fi

fi
.

GENERAL NOTES
1. The app should include a robust caching technique

2. Obeying Clean-Code Architecture, S.O.L.I.D Principles, and using different design patterns is a big
plus

3. You should pick a software architecture pattern, (i.e MVP, MVVM,VIPER) that you think ts this task
and tell us why you choose this patter

4. Write unit tests for your code and try to cover as much as you ca

5. Using third parties is OK, but be selective .

6. You will deliver source code that should compile without any errors or warnings .

7. Commit as you go , we want to see your progress. Don’t do a single commit of the whole
solution .

8. The web services that you are going to use :

• Event Types :
http://private-7466b-eventtuschanllengeapis.apiary-mock.com/eventtypes

• Event Listing :
http://private-7466b-eventtuschanllengeapis.apiary-mock.com/events?event_type ={type of the
event}&page={1,2,3}

i. event_type = the type of the event that will be returned from event types web service.

ii. page = the pagination of the event listing web service, since the maximum number of pages
of each event listing will be 3 pages.
.

fi
Wireframes :

Event screen Event Details screen

You might also like