Text columns can hold four different types of text in your app:
Plain text
Rich Text
Emojis
Email Addresses
Plain text
A plain text column holds exactly that—plain, unformatted text values. This can be used for a wide range of purposes such as storing names, locations, addresses, roles, comments, notes, tasks, days of the week, months of the year, etc. Your text can also include emojis.
You can display this information in your app using various Components, or as Column Values when setting up Collections and components. The appearance of the plain text values in your app depends on the formatting options available for the chosen component.
Rich Text
A rich text column holds text that can be formatted or styled as italic text, bold text, headers, bullet points, numbered lists, links, and more using Markdown syntax. Values in a rich text column can be displayed with the specified styling using the Rich Text Component in your app.
For an in-depth explanation of what Markdown is and how to use it, check out the Markdown Guide. If you'd like to try a browser-based Markdown text editor, try StackEdit.
Emoji
An emoji column can hold one or more emojis as well as plain text. If you use multiple emojis in a row (or emoji and plain text), you can display the information in your app in the same way as you would display plain text values.
You can also display emojis in this column as the image in a collection component. When configuring the component, select the emoji column as the Column Value in the image field. Glide will use the emoji as the image for that collection item. If a row has more than one emoji in the column, Glide will use the first emoji as the image.
An email column holds email addresses. You can display the values in this column in your app using any component that displays a text value or as Column Values when setting up collections and components. You can use the values in this column in multiple Actions like Send Email and Compose Email, as well as with integrations like Gmail and Microsoft Outlook.
Email addresses in a table can also be used in Forms so that, when a user who’s signed in to your app submits a form, they don’t need to manually share their email address with you.