A Closer Look at the Wadiz App Development Team

Hello, I’m an Android developer on the Wadiz App Development Team.
I think one of the things developers care about most is development culture. So! Here’s a look at the development culture of Wadiz 😆

Code review time—something every developer wants to do

Speaking of Android coding conventions prior to code reviews, we use the following:

• Branch names use the issue number as a prefix
• Write according to the coding guidelines
• Write PRs according to the template

I’ve attached the necessary links, such as the Jira issue link, design link, and planning document. Please also include a description of the work you’ve done so that reviewers can easily understand what changes were made in this PR.

During code reviews, we check and discuss whether the code clearly conveys naming conventions, branching conditions, and the use of flag values. If there’s any logic you’re unsure about, feel free to share it so we can discuss it together. We help each other write code that can be improved.

Branch Strategy

The Wadiz Android team uses our own branching strategy.

1. Create a feature branch for each issue. That feature branch is created from the develop branch.
2. If the feature is large, create a sub-branch for the smaller portion and submit a pull request.
3. Once the feature is complete, submit a pull request to the `develop` branch. A week before deployment, we freeze the code and create a release branch.
4. Once the release branch is deployed, it is merged into the main branch, and the develop branch is updated to match the main branch.

Easy Testing in Developer Mode

We're developers! Let's automate the tedious stuff!

When deploying internally for QA, we use automation. When a task is run, it uploads the test app to Firebase and sends a message to the Slack channel confirming the deployment.

How do I test it?

The app development team has enabled developer mode to allow for server changes during app testing. We provide a debug view that lets you monitor API calls.

Tech Sharing Session

We share new technologies and what we’ve learned during team meetings. The Android team discusses topics such as how they implementedmotionLayout and encoding—which were used for the first timein the app’sInstagram sharing feature—how they designed the logic when implementing the feature, and how these new technologies can be applied in practice.

The app development team works on both iOS and Android. We also hold sessions to share insights on the technologies used and how they function not only on Android but also on other operating systems.

That's a great idea!

The biggest strength of Wadiz is that we actively share ideas and turn them into projects. We take the initiative to propose ideas and create proof-of-concepts to share with the team. It’s not just a side project—you’ll have the opportunity to implement the features you want to see in Wadiz actual Wadiz!