Welcome to the Medibank iOS coding challenge! This is your opportunity to demonstrate your skills in SwiftUI, app architecture, modular development, and testing practices by building a small yet complete iOS app.
You are not expected to build a production-level app. Instead, we’re looking at how you structure your code, prioritise tasks, and communicate trade-offs. Develop a proof-of-concept news reader app using SwiftUI. The app will fetch and display trending articles from NewsAPI, allow users to filter by sources, and support saving articles for later reading.
Your app should include a TabView with three tabs:
- Displays a list of articles based on selected sources
- Each row should include: title, description, author, and thumbnail image
- Tapping a row should open the article in a WebView within the app
- Users should be able to save articles from this view
- Handle empty states gracefully (e.g., no sources selected, no results)
- Displays a list of available article sources (English only)
- Allow users to select multiple sources
- Selection should persist across app launches
- Displays a list of articles previously saved by the user
- Tapping a saved article should open it in a WebView
- Users should be able to delete saved articles
- Saved articles must persist across app launches
- Use NewsAPI to fetch headlines and sources (https://newsapi.org/)
- Register for a free API key
- API will return the latest 10 articles per source — pagination not required
- Use URLSession or a custom networking layer
- Do not use any 3rd-party NewsAPI clients
- Follow MVVM architecture
- Uses SwiftUI property wrappers appropriately to manage state, observable data, and shared dependencies, ensuring correct ownership and predictable UI updates.
- Structure your code to promote modularity and reusability, where applicable
- Use any local persistence method (e.g.,
UserDefaults, local file, CoreData) - Clearly separate persistence logic for readability
- Unit Tests: Cover ViewModels, business logic, and API service
| Category | Details |
|---|---|
| SwiftUI Usage | Clean, idiomatic use of SwiftUI and data/state flow |
| Architecture | Scalable structure with clear separation of concerns |
| Persistence | Local storage for sources and saved articles |
| Testing | Unit tests provided; optional UI/snapshot tests |
| Code Quality | Modular, readable, and well-documented code |
| UX & UI | Responsive UI, smooth navigation, and empty state handling |
- Xcode 26
- Swift 5.9+
- Swift Package Manager (SPM) for dependency management
You have 3 days to complete the challenge. We encourage you to focus on delivering what’s most meaningful and practical within the available time:
- A working implementation of the core functionality
- A clear and modular SwiftUI architecture
- A thoughtful approach to data flow and local persistence
- Reasonable test coverage for the business logic (e.g., ViewModels)
You are free to decide the order and approach for implementing the features. The goal is to understand your ability to drive a solution end-to-end, make trade-offs, and demonstrate solid engineering principles.
- Develop your solution in your own codebase
- Complete and submit your project within 3 days of receiving it
- Share a link to your completed project using any code sharing platform (e.g., GitHub, GitLab, Bitbucket, or similar)
We look forward to reviewing your code. If you have any questions, feel free to reach out.
Good luck, and have fun building! 🚀