Android developers
Kotlin and Jetpack Compose. Wire the app to the API, add maps, make SOS dependable.
Contribute
Build this with us.
Nayki is an open-source project for safer, better-informed travel. The idea is solid and the foundations are in the repository, but it needs more people than one team to become real. If you build software, run a safety programme or know your city's streets, there is a place for you here.
Fig. 4 How the project grows. Contributors arrive and plug into modules (app, API, data, map, SOS). The dashed slot marked YOU is open: that is where you join.
Who we need
Seven kinds of help.
Backend developers
FastAPI, PostGIS and H3. Harden the endpoints, add CI, improve the safety engine.
Data and GIS people
Open data, OpenStreetMap, government datasets. Help decide which sources are trustworthy and how to weigh them.
Designers and accessibility
Clear risk language, calm screens, screen-reader and low-vision support, flows that work under stress.
Safety, civic and NGO teams
People who work on women's, commuter or community safety. Tell us what is missing and what would be harmful.
Privacy and security reviewers
Review how location, reports and SOS data are handled, and break it before someone else does.
Testers in real cities
Walk the routes, check the help points, tell us where the data is wrong.
Start here
Good first jobs.
These are real gaps in the repository today. Pick one, say so in an issue, and go.
Connect the Android app to the backend and replace the sample data.
Rename the Android package from com.example.nayki.
Add CI that runs the backend tests on every pull request.
Evaluate open data sources for one city and document their coverage.
Run an accessibility review of the existing screens.
Translate the app strings into a second language.
How to join
Four steps.
- Read the repository
Start with the README, then
nayki-backend/README.mdfor the backend rules. - Open an issue
Tell us who you are, what you can do and what you want to pick up. Teams and organisations are welcome.
- Fork and branch
Make your change on a branch in your fork. Keep it small and focused.
- Open a pull request
Describe what changed and how you checked it. Backend changes should keep
make testpassing.
Principles
Rules every contribution follows.
Never claim "safe"
No route, place or area is called safe or secure, in code, copy or marketing.
Say when we do not know
No data means "unavailable", never an invented score.
Collect less
Location is sensitive. Keep it out of logs, aggregate it, and delete what is not needed.
Label the status
Prototype, simulated or real: documents and screens say which. No fake demos.
Teams and organisations
Working together.
If your team wants to co-build, pilot Nayki in a city, contribute data, or review the design, write to us. Say what you do, what you can offer and what you would need.
- Public conversation: GitHub issues.
- Direct contact: transmission@theshriks.space.
- Nayki is not an emergency service. For urgent help, always call your local emergency number.