{"id":4287,"date":"2022-03-22T11:05:00","date_gmt":"2022-03-22T11:05:00","guid":{"rendered":"https:\/\/blog.tchop.io\/?p=4287"},"modified":"2024-08-14T06:36:38","modified_gmt":"2024-08-14T06:36:38","slug":"you-have-the-choice-article-as-link-or-directly-native-in-the-app","status":"publish","type":"post","link":"https:\/\/blog.tchop.io\/en\/you-have-the-choice-article-as-link-or-directly-native-in-the-app\/","title":{"rendered":"You have the choice: article as link or directly native in the app"},"content":{"rendered":"\n
\"User<\/figure>\n\n\n\n

Some features<\/a> are small and inconspicuous, but reveal a great added value. The ability to embed any web links or articles natively in the app with just a few clicks is one such feature. Today we want to explain in more detail how this works.<\/p>\n\n\n\n

Native UX or Web View<\/h4>\n\n\n\n

The preferred, because easiest way to display content<\/a> in your own app is the so-called article map (see also here<\/a>). Here, the content or article is opened in the app in a web view. The teaser elements can be easily edited and customized, and at the same time the integration works for practically all content that is accessible in some way on the web – without the need for complex integration. Even paywall-protected, own content can be made available with a few tricks.<\/p>\n\n\n\n

From a mobile UX perspective, however, it is always better to integrate content directly, i.e. natively, in the app. There is no need to load the text of the article, it is immediately available. Loading time is practically eliminated. The user remains technically native in the app. If you want to use this automatically for your own integration, for example, you need to connect a form of interface that allows you to transfer all the necessary content to tchop.<\/p>\n\n\n\n

You can compare the two options here in the video.<\/p>\n\n\n\n

\n
\n
\n
\n
\n
\n