Text in your apps

Last updated Invalid Date

When we talk about text or copy, we mean more than the marketing copy on your landing page or text for your call-to-action buttons. Text in your apps means any hardcoded, non-user generated text. Some examples include:

  • Push notification text
  • Transactional email text
  • Menus on your mobile, web, or VR app
  • Settings text labels on your smartwatch app
  • The documentation you're reading, etc.

Apps and developer time can get weighed down not only by text maintenance, but also media. If it's not code, consider if it belongs in your repo. Tipe can help you manage your text and images by pulling them out and using our CDN to serve them. Save yourself time by giving creative team members direct access and ownership of text and images and never hard code text again.

Hardcoded text

If your text lives in the same repo as your app, then it's hardcoded.


    <!-- the following text is hard coded -->
    <h1>Hello, welcome to our app!</h1>

Hardcoded text slows you and other developers down because now you're responsible for that text. You'll be updating the punctuation, spelling, i18n, and other changes. You'll probably have to redeploy your apps for each update, too.

Dynamic text

When all your app's text is comprised of variables with their values stored in some other system, you never need to know or care about what those values are. You only need to know where to put the text and images.


    <!-- the following text is dynamic -->
    <h1>{{ text.heading }}</h1>

Although this text is dynamic, the text itself may still live in the repo, most likely in a variable somewhere or even a JSON file. If the text is still in your code, you still have to manage it.

Coding is hard and developers are expensive for companies. It takes valuable time to build apps and if your superpower is coding, you should be coding, not writing copy. Tipe helps you pull all of the text and images out of your app and gives ownership of those areas to creative team members. This frees you up to focus on what you do best — code.

Dynamic text API

To truly relieve yourself from having to manage text, your text needs to be behind an API and completely removed from your apps so you can pull it in when you need it. From there, it's up to you on how you consume the text API; build-time, runtime, or combination of both.

Go further

Learn about Documents and how to query them with GraphQL or REST.