The team behind the code
Barel works as one team across 7 disciplines. Each project gets people from the disciplines it needs, working together from the first design to the store release.
Who writes what
Every discipline and the languages it works in. Scroll sideways on a small screen.
| Discipline | Kotlin | Java | Swift | Objective-C | Dart | TypeScript | JavaScript | Python | Go | C# | C++ | SQL |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Android engineering | Not used | Not used | Not used | Not used | Not used | Not used | Not used | Not used | ||||
| iOS engineering | Not used | Not used | Not used | Not used | Not used | Not used | Not used | Not used | ||||
| Cross-platform | Not used | Not used | Not used | Not used | Not used | Not used | Not used | Not used | ||||
| Game development | Not used | Not used | Not used | Not used | Not used | Not used | Not used | Not used | Not used | Not used | ||
| Backend and data | Not used | Not used | Not used | Not used | Not used | Not used | Not used | |||||
| Product design | Not used | Not used | Not used | Not used | Not used | Not used | Not used | Not used | Not used | Not used | Not used | |
| Quality and release | Not used | Not used | Not used | Not used | Not used | Not used | Not used | Not used |
Disciplines
Designers, engineers and testers sit in one team, so a question about a screen, a query or a store rule gets answered the same day.
Android engineering
iOS engineering
iPhone and iPad apps, widgets, purchases and App Store submissions.
Cross-platform
Shared codebases for both stores, with native modules where needed.
Backend and data
APIs, sync, databases, admin panels and release automation.
Product design
Flows, interfaces, prototypes and design systems developers can build from.
Quality and release
Test plans, automation, device testing and store rollouts.
How we work together
On a project, design, development and testing overlap rather than hand off. A designer stays involved while screens are built, a tester reviews flows before code exists and engineers join discovery calls when technical constraints shape the product.
Knowledge is shared through code review, written decisions and short demos at the end of each iteration, so a project never depends on a single person remembering how something works.