Submission Notes

The branch are named to consist of the number they are in their stack and also the number they are in the general readme. It is named in order ${stack}-{No in stack}-{No in general}. For example FE-task1-task3.

Due to tasks depending on each other, merge in this order:

1. #12 - Merges the 4th task to the 5th overall question

2. #10 - Merges the 5th task to the 3rd overall question

3. #9 - Merges the 3rd task to the 2nd overall question

4. #8 - Merges the 2nd task to the 1st overall question

5. #7 - Merges the 1st into main

---

Mobile Dev Challenge

Welcome! 👋

This is the Mobile Developer Challenge repo for testing candidates at LabLambWorks. The challenge is broken up into clear backend and frontend sections and your work should be submitted as multiple pull requests.

---

🔗 Repo

Fork this repo: https://github.com/LabLambWorks/mobile-dev-challenge

You will work directly in your fork.

---

📋 Tasks

There are 6 small tasks in total — 3 Backend and 3 Frontend:

📦 Backend Tasks

Found in Backend-Task.md

1. Add reviewsCount Field
2. Add spicinessDescription Virtual Field
3. Add Hooks for reviewsCount Field (lastReviewedAt, prevent decreasing count)

📱 Frontend Tasks

Found in Frontend-Task.md

1. Filter Noodles by spicinessLevel and originCountry
2. Leave Review Button (linked to reviewsCount)
3. Local Favourites Feature

---

✅ Submission Instructions

Submit your work as 5 pull requests to your private repo, one for each of the grouped tasks:

Task Group	PR Description
Backend Task 1	Add reviewsCount field to InstantNoodle
Backend Task 2	Add spicinessDescription virtual field
Frontend Task 1	Add filtering by spiciness and country
Frontend Task 3	Add local favourites feature
Backend Task 3 + FE Task 2	Add review functionality with hooks

---

🔒 Privacy & Access

Please make your forked repository private, and then:

• Invite @Sam-Lam-LabLambWorks as a collaborator so we can access your submission for review.

---

⏱️ Time Expectations

Although there are 5 pull requests, each task is small and focused.

💡 With AI assistance, this entire challenge should take less than fews hour to complete. (Time is not a requirment)

We care more about code clarity, correctness, and attention to detail than how fast you finish.

---

🧪 Testing

• You can run the Keystone backend locally and use the GraphQL Playground to test your schema and mutations.
• The frontend runs on Expo and can be tested on an emulator or device.

---

🧼 Guidelines

• Keep your code clean and modular.
• Reuse components where possible.
• Handle loading and error states gracefully.
• Follow the task instructions precisely.

---

Good luck, have fun, and show us what you’ve got! 🎉