Explore

Onboarding Guide – Support Developer

1. Welcome & Introduction

About Masai Code Studio: Small, fast-moving app studio building cross-platform apps for consumers

Team Structure: Sole developer (lead), Support Developer (you), Graphic Designer (Mvoi), Growth Marketer (Thomas).

Development Style: Lean, fast iterations, with clean maintainable code and practical solutions.

⁠

2. Tools & Setup

Communication & Workflow

Primary Communication: WhatsApp

Task Management: Coda

Code Hosting: GitLab → repo access will be shared.

Development Setup

Code Editor: VS Code recommended (extensions list will be shared).

Mobile Development: Flutter (confirm which one your studio uses).

Backend Development: NestJS / Node.js (include repo + setup steps).

Database: Postgres + MongoDB (credentials provided via [vault/1Password/secure note]).

Environment: Use .env.example for local setup. Ask for secrets if missing.

Docker: Used for local backend services (Redis, Postgres, etc.) – run docker-compose up.

⁠

3. Coding Standards & Workflow

Branching Model:

main → production

dev → staging / active development

Feature branches: feature/<name>

Bugfix branches: fix/<name>

Commit Style: Conventional commits (e.g., feat: add search API, fix: mobile crash on login).

Pull Requests:

Small, focused PRs preferred.

Always include description & testing notes.

Code Reviews: Lead developer (you) will review.

⁠

4. Responsibilities Breakdown

Mobile:

Implement UI screens from provided designs.

Integrate with backend APIs.

Fix crashes, handle performance tuning.

Backend:

Implement API endpoints.

Write queries for Mongo/Postgres.

Debug and resolve backend issues.

General Support:

Write tests where applicable.

Update docs for features you touch.

Monitor and fix bugs.

⁠

5. First Week Plan

Day 1–2

Set up local environment (backend + mobile). (Done)

Walk through existing repos with lead developer. (

Review API documentation and mobile app structure.

Day 3–4

Pick first small task (bug fix / small feature).

Get comfortable with branching, commits, and PR flow.

Day 5

Demo first contribution.

Feedback session + adjustments.

⁠

6. Expectations

Communication: Ask questions early, don’t get stuck.

Delivery: Small, iterative contributions over big untested changes.

Documentation: Update readmes, APIs, and wiki when you add/change something.

Growth: You’ll gradually take on more independent tasks as you ramp up.

⁠

7. Resources & References

[Repo links + access details]

[API Docs or Swagger link]

[Design files (Figma, XD, etc.)]

[Credentials / secrets sharing method]

[Coding guidelines doc]

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.