Project & Team Naming Best Practices

Project & Team Naming Best Practices

Localization can become a complicated and messy process. Here at Applanga, we want to empower you to take control of your app localization and keep you organized along the way.

Applanga users often start with just a project or two under one team. As users complete their localization deliverables, they usually add more projects and teams to keep their processes organized. Oftentimes, users add projects with names created on the fly. As more and more projects and teams are added to an Applanga user’s dashboard, inconsistent or non descriptive naming can cause confusion for other Applanga team members.

To help keep you organized we compiled a list of 5 best practices. These are not hard rules, but instead helpful guidelines for keeping your Applanga space organized.



1 - Develop Proper Naming Schemes

A proper naming scheme is important because it will help keep your projects and teams organized. You don’t want to end up in a situation where one project uses an app’s abbreviation, another uses an internal phrase, and yet another is just named “project 3.” Naming schemes can be based on what helps your Applanga users quickly identify projects and teams. Effective project naming schemes often include the company’s name, the application’s name, and the platform. While practical team names can include the department name, the company’s name, the projects included under a team, or any combination to help you manage project access.


2 - Use Meaningful Names

Your project and team names should reflect its scope. This is especially important when you are managing translations for different products on Applanga. Meaningful project and team names help ensure proper access for users. It also helps prevent confusion when translators and other team members need to work on specific projects.

Avoid names like Project 1, Project 2, Project 3. Instead, try to create names that reflect the scope, platform, and other relevant information. Meaningful names will allow users to easily distinguish between different projects and teams on the Applanga dashboard.


3 - Use Unique Names

Reusing similar names can create confusion for Applanga users. Unique names across projects and teams ensures proper access for users, smooth collaboration on projects, and prevents delays from working on the incorrect project.


4 - Keep External Users in Mind

Are you working with people outside of your organization? Maybe a translation agency, outsourced development team, or external reviewers? External partners may not know your company’s lingo and phrases so it's important to keep this in mind when creating collaborative projects and teams. Appropriately named projects can reduce the back and forth questions and clarifications. Using unique and meaningful names will help your external partners support your goals.


5 - Archive or Remove Unused Projects and Teams

If your Applanga dashboard is feeling cluttered, you can always remove any unused projects or teams. Users with enterprise level plans can request support to archive their old, unused projects. If you don’t have a paid plan, you can also export all your translations and delete the project. This is helpful for cleaning up projects that are no longer in use. It also opens up a project for use with other applications which require localization.



We hope these best practices help keep you and your projects organized. We understand following all recommendations isn’t required or may not be possible, but keeping them in mind may still prove useful. If you want to update names after reading this post, no problem! Project names can quickly be updated in the project settings. Just be sure to click Update at the bottom of the settings page to save your changes. To update a team’s name, navigate to the team’s page then click the Edit button on the team’s header.