Developed for the AQA Computer Science GCE 7517 as the Non-Examined Assessment coursework project, under the title "Outdoor activity tracking & discovery app".
I wouldn't recommend using particularly any of the code in the project. Much of it doesn't follow good practises, some of it has bugs, some of the code (like the API/server stuff) is a mess. But it was written to be quick to build, only stand-up to brief inspection, and hit as many of the requirements and recommendations of the AQA specification as possible - it does get quite a few.
If you're reading this trying to do your NEA: add features that don't hit anything on the technical requirements (e.g. design and basic code), then write about them. They may not give marks for the implementation, but they can allow you to access marks in the writeup. A lot of the writeup focuses on design decisions - these don't count for anything by themselves. For example, saying "it looks nice" gives no marks for implementation and no marks for writeup. But saying "the button looks nice and is big and bold to attract the user's attention, making the next actions obvious" seems to work. If you're doing this, consider reading some design guidance, such as https://m3.material.io/ & https://developer.apple.com/design/human-interface-guidelines/.
The writeup documents the project.
Result was 73/75 for the NEA, and an A* overall.