Skip to main content

Team collaboration

Work together on Appifex projects with your team.

Sharing projects​

Invite team members​

  1. Open your project
  2. Go to project settings
  3. Click Share
  4. Enter teammate's email
  5. Select permission level

Permission levels​

RoleViewEditDeployManage
Viewer✓---
Editor✓✓✓-
Owner✓✓✓✓

Coder mode for teams​

Coder mode is designed for team collaboration:

Parallel development​

Team members can work on different features simultaneously:

Developer A: session/add-authentication
Developer B: session/redesign-dashboard
Developer C: session/mobile-app

Each session is isolated with its own:

  • Git branch
  • Database schema
  • Preview URLs

Code review workflow​

  1. Developer creates session and builds feature
  2. Creates pull request when ready
  3. Team reviews on GitHub
  4. Merge when approved
  5. Changes go to production

Two-way GitHub sync​

Edit anywhere​

Team members can work in their preferred environment:

In Appifex:

  • Visual progress tracking
  • AI assistance
  • Instant deployment

In IDE (VS Code, Cursor, etc.):

  • Familiar tooling
  • Local development
  • Full debugging

On GitHub:

  • Code review
  • PR discussions
  • Issue tracking

Sync flow​

Appifex → GitHub ← Local IDE
    ↓         ↓         ↓
   Push     Sync      Push
    ↓         ↓         ↓
    └────────→←────────┘

All changes sync automatically via Git.

Database isolation​

In Coder mode, each session gets its own database schema:

main branch      → public schema (production)
session/auth     → session_abc123 schema
session/mobile   → session_def456 schema

Why this matters​

  • Safe testing - Won't affect production data
  • Parallel work - No conflicts between sessions
  • Clean merge - Schema migrations handled automatically

Communication​

In Appifex​

  • View activity on shared projects
  • See who made recent changes
  • Track deployment history

External tools​

Integrate with your existing workflow:

  • GitHub - Code review and discussions
  • Discord - Our community for questions
  • Slack - (coming soon) Notifications

Best practices​

Use descriptive session names​

Good:

  • add-stripe-payments
  • fix-login-bug
  • redesign-settings

Not helpful:

  • my-changes
  • test
  • feature

Communicate about shared code​

Before making big changes:

  1. Check if others are working in related areas
  2. Discuss approach if needed
  3. Create focused sessions

Review before merging​

Use the diff view to see all changes:

  1. Open session
  2. Click View diff
  3. Review changes vs main
  4. Create PR for team review

Keep main stable​

  • Test thoroughly in session branches
  • Get code review before merging
  • Fix issues before they reach production

Project organization​

For small teams (2-5)​

  • Single project with multiple sessions
  • Direct communication
  • Quick iterations

For larger teams​

  • Consider separate projects for distinct products
  • Establish review requirements
  • Use consistent naming conventions

Troubleshooting​

Conflicting changes​

If two sessions modify the same code:

  1. Git handles most conflicts automatically
  2. For complex conflicts, review on GitHub
  3. Resolve manually if needed

Session out of date​

If main has progressed:

  1. Click Sync with main in session
  2. AI merges latest changes
  3. Continue development

Permission issues​

If you can't access a project:

  1. Ask the owner to check sharing settings
  2. Verify your email matches the invitation
  3. Try signing out and back in