Form Design & Project Implementation
Welcome to the Implementer section! Whether you're a form designer, project manager, or NGO leader, this guide covers everything you need to design forms, manage projects, and deploy ODE in your organization.
Who This Guide Is For
This section is designed for users who:
- Are designing data collection forms
- Are planning and managing ODE projects
- Want to customize forms for specific workflows
- Need guidance on deployment and data management
- Are responsible for project outcomes
If you're collecting data with Formulus, see the Data Collector Guide.
If you're developing or extending ODE, see the Developer Guide.
Quick Start
Get your first form running in 30 minutes:
- Understand the Basics - Learn how forms and projects work
- Design Your First Form - Create a form using JSON schema
- Deploy Your Form - Get it to field workers
What You'll Learn
Implementer Overview
Understand your role and project planning basics.
Get Started →Form Design Guide
Master JSON schema and UI design patterns.
Learn More →JSON Forms Reference
Complete reference for form controls and validation.
Reference →Deployment Guide
Steps to deploy forms to field teams.
Deploy →Data Management
Collect, review, and export data securely.
Learn More →Troubleshooting
Fix issues with forms, sync, or deployment.
Get Help →Documentation Roadmap
🎓 Learn the Concepts
Design Forms
- Form Design Principles
- JSON Schema Basics
- UI Schema for User Experience
- Form Controls Reference
- Validation Rules
Advanced Form Features
Deployment & Operations
Data Management
🔧 Configuration
Key Concepts
The ODE Workflow
1. Design Forms (You)
↓
2. Create Project (Server Setup)
↓
3. Distribute App (Field Teams)
↓
4. Collect Data (Workers)
↓
5. Sync to Server (Automatic)
↓
6. Review & Export (You)
↓
7. Analyze Data (Your Tools)
Form Design Philosophy
ODE forms are JSON-based, which means:
- ✅ Forms are portable (no proprietary format)
- ✅ Forms are version-controlled (git-friendly)
- ✅ Forms are human-readable
- ✅ Forms support complex validation
- ✅ Forms work offline seamlessly
Your Responsibilities
As an Implementer, you typically:
| Task | When | Tool |
|---|---|---|
| Design forms | Project planning phase | JSON editor + ODE reference |
| Create app bundle | Before deployment | Synkronus CLI or portal |
| Distribute to workers | Pre-launch | Formulus app or direct installation |
| Monitor submissions | During collection | Synkronus portal |
| Export data | After collection | Synkronus CLI or custom scripts |
| Review quality | Ongoing | Your analysis tools |
Common Scenarios
Scenario 1: Health Survey
You're conducting a community health survey with 50 field workers across a region with limited connectivity.
→ See the Health Survey Template Guide
Scenario 2: Multi-Form Campaign
You're managing a 3-form workflow where later forms depend on earlier responses.
→ See Forms with Conditional Logic
Scenario 3: Offline Deployment
You need workers to collect data with zero internet connectivity for extended periods.
→ See Offline Deployment Guide
Scenario 4: Large-Scale Rollout
You're deploying to 1000+ workers across multiple countries.
→ See Scaling & Infrastructure
Terminology
| Term | Meaning |
|---|---|
| Form | A survey/questionnaire defined in JSON |
| Project | A collection of forms and workers under one management |
| App Bundle | A packaged set of forms distributed to workers |
| Submission | One completed form response |
| Sync | Sending submissions from device to server |
| Formular | The mobile app workers use |
| Synkronus | The server storing data |
| UI Schema | Instructions for how to display a form |
| Validation | Rules that check if data is correct |
Before You Start
You should have:
- ✅ Understanding of your data collection workflow
- ✅ List of form fields needed
- ✅ Access to ODE server (or instructions for setup)
- ✅ Basic familiarity with JSON (or willingness to learn)
- ✅ Access to your field team for testing
Getting Help
If you need assistance:
- Check the form design guide → Form Design Guide
- Look up a control type → Form Controls Reference
- Review deployment steps → Deployment Guide
- Contact the community → Get Help
- Report an issue → GitHub Issues
Next Steps
Ready to start designing? Let's begin!
Or jump straight to form design:
- Start with a simple form to test your workflow
- Involve your field team in form design (they know what works)
- Plan for data quality checks from the beginning
- Test in offline mode before large-scale rollout