{
    "version": "https:\/\/jsonfeed.org\/version\/1",
    "title": "ivan's blog: posts tagged tinkoff",
    "_rss_description": "It is my diary. I’m ivan zviahin, an designer, manager, car enthusiast.",
    "_rss_language": "en",
    "_itunes_email": "ivanzviahin@gmail.com",
    "_itunes_categories_xml": "",
    "_itunes_image": "http:\/\/www.ivanzviahin.by\/blog\/user\/userpic-square@2x.jpg?1711411913",
    "_itunes_explicit": "no",
    "home_page_url": "http:\/\/www.ivanzviahin.by\/blog\/tags\/tinkoff\/",
    "feed_url": "http:\/\/www.ivanzviahin.by\/blog\/tags\/tinkoff\/json\/",
    "icon": "http:\/\/www.ivanzviahin.by\/blog\/user\/userpic@2x.jpg?1711411913",
    "author": {
        "name": "Ivan Zviahin",
        "url": "http:\/\/www.ivanzviahin.by\/blog\/",
        "avatar": "http:\/\/www.ivanzviahin.by\/blog\/user\/userpic@2x.jpg?1711411913"
    },
    "items": [
        {
            "id": "193",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/feed\/",
            "title": "New feed entry point · Tinkoff",
            "content_html": "<p>How we made the personal feed in the bank app more readable by increasing 1-week feed retention rate several times over.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/feedmain.jpg\" width=\"2560\" height=\"1918\" alt=\"\" \/>\n<\/div>\n<p><a href=\"https:\/\/apps.apple.com\/RU\/app\/id455652438\">Tinkoff<\/a> is an online ecosystem or super app based on financial and lifestyle services. The best mobile privetely-held bank in the world according to Global Finance. The third largest bank in the CIS with 30,000,000 customers.<\/p>\n<p>A personal feed is a product. With the help of which we are building a communication platform where people learn all about finance, save money and have fun. Businesses need a personal feed to sell financial products through it. Users need to have fun, learn something new, be part of an expert community. In simple words, it’s just a feed of events and news.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-old.jpg\" width=\"2541\" height=\"2031\" alt=\"\" \/>\n<\/div>\n<p>The personal feed is having a positive impact. We test disabling the feed on new users and compare metrics across our products. There has been a drop in metrics, including cashback, bonuses and airline tickets. The product is working well, but we need to make it more efficient.<\/p>\n<p>The feed is in a difficult-to-reach place on the interface. To get to it, you have to open the “City” tab, which doesn’t tell you what’s on there. You have to look at a complicated screen and open the bottom sheet with the feed.<\/p>\n<p>People say the feed is hard to find. If people can’t access the feed, they won’t come back. If they don’t come back, they won’t use the product.<\/p>\n<p>By comparison, the stories on the home screen get visited several times more often and people come back more often, even though both are feeds with content, just in different formats.<\/p>\n<h2>Problem for users<\/h2>\n<p>We want to make the feed accessible. To make you more likely to open the feed on the mobile app. It’s heavily hidden at the moment.<\/p>\n<h2>Problem for business<\/h2>\n<p>Increase retention rate in the feed. If we increase the retention rate in the feed, customers will be more engaged with our products. If customers use more products, the bank will make more money.<\/p>\n<h2>Audience<\/h2>\n<p>The audience is very wide and diverse. But we aimed at all our bank users with an active lifestyle. I can’t share the audience of the personal feed, but it makes up the majority of the total number of customers. Considering that we have 30,000,000 customers, the scale of the product is confirmed. Wow!<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-audience-dia-3.jpg\" width=\"2541\" height=\"873\" alt=\"\" \/>\n<\/div>\n<h2>Success criteria<\/h2>\n<p>↑ 1-week feed retention rate<br \/>\n↑ 1-week app retention rate<br \/>\nWe also need to keep people engaged in the feed, which will be difficult.<\/p>\n<h2>Discovery<\/h2>\n<p>We’re looking for a solution in other products, but we haven’t found any yet. So, we’ll have to come up with a solution ourselves. We looked at what our users had to say. We’ve put together a job spec for a Data Analyst. But...<\/p>\n<p>But I find interesting is this. It’s not just about moving the feed. How do you get people to go there? The analysis shows us this:<\/p>\n<ol start=\"1\">\n<li>We already have a big audience that goes to the bank every day. We just need to put the feed on the home screen and get people interested.<\/li>\n<li>We already have content on the home page in the form of Stories, which is a great product.<\/li>\n<\/ol>\n<p>So, what we have<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-2.jpg\" width=\"2541\" height=\"579\" alt=\"\" \/>\n<\/div>\n<p>This scheme helped us make some guesses.<\/p>\n<h2>Hypothesis formulation and low-fi prototypes<\/h2>\n<p>These are the hypotheses.<\/p>\n<ol start=\"1\">\n<li><b>Main screen.<\/b> Adding the feed to the home screen will make it easier to access and more likely to be used.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i1.jpg\" width=\"2541\" height=\"1923\" alt=\"\" \/>\n<\/div>\n<ul>\n<li>We had many more options than I’m going to show you. I’ll show you the best ideas and how they look. I thought the best idea was to put content in a separate tab.<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i1-1.jpg\" width=\"2541\" height=\"1878\" alt=\"\" \/>\n<\/div>\n<ul>\n<li>We stopped because we realised it was unrealistic to expect people to read content on secondary screens in the bank. We tried adding stories to secondary screens. It doesn’t work. Right, let’s move on.<\/li>\n<\/ul>\n<ul>\n<li>The second idea was to just put the feed under all the accounts, as there aren’t that many of them on average.<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i1-2.jpg\" width=\"2541\" height=\"1878\" alt=\"\" \/>\n<\/div>\n<ul>\n<li>We saw that people don’t scroll past the second screen. How can we open it from the first screen? We added a right swipe option.<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i1-3.jpg\" width=\"2541\" height=\"1878\" alt=\"\" \/>\n<\/div>\n<ul>\n<li>It’s cool, but it looks complicated. It’s not natural. Turn the story feed into a smart widget.<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i1-4.jpg\" width=\"2541\" height=\"1878\" alt=\"\" \/>\n<\/div>\n<ul>\n<li>Interesting idea, but we don’t have the guts to do it. There’s a big risk we’d mess up the stories and it’d all fall apart. But on day five, we had a brainwave...<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i1-5.jpg\" width=\"2541\" height=\"1878\" alt=\"\" \/>\n<\/div>\n<ul>\n<li>It’s much more straightforward to swipe down than to swipe right. Pull to refresh is no longer necessary as all the data is updated in real time. It seems to be the best idea, so we’ve decided to go with it. And opening quick tools works the same way in iOS, which gave us the green light to go ahead with it.  We showed this idea to everyone who was interested: the product managers, the designers and the stakeholders of the home screen. We got a few doubts in response, but everyone was generally on board with this solution. We gave this to user testing, and we were pleased with the results. Let’s consider some other possibilities.<\/li>\n<\/ul>\n<ol start=\"2\">\n<li><b>Interest.<\/b> Make an entry point interesting to increase its open and retention rate.<\/li>\n<\/ol>\n<ul>\n<li>The simplest way to get people interested is to create an information trigger on the outside. I think stories are probably the best trigger, but it’s tricky to make stories and a feed one platform. It’ll probably be a separate story soon.<\/li>\n<li>But for now, we just need something simple. And here’s the thing: if you’ve been keeping up with our content, you’ll have noticed that we recently added a <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/news-card\/\">news card in the feed.<\/a> It would be great to take the most interesting words from the introductory text and put them outside.<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i2.jpg\" width=\"2541\" height=\"1809\" alt=\"\" \/>\n<\/div>\n<ul>\n<li>Let’s move on to the next item on the agenda.<\/li>\n<\/ul>\n<ol start=\"3\">\n<li><b>Clear.<\/b> Make the opening of the feed simple and clear to increase accessibility.<\/li>\n<\/ol>\n<ul>\n<li>Somehow we have to teach people how to use the new feed. At first we tried to come up with some kind of detailed training, but then we realised that the easiest way to do was to just pull the feed a few times. And stop when the person has done it.<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i3.jpg\" width=\"2541\" height=\"1968\" alt=\"\" \/>\n<\/div>\n<ol start=\"4\">\n<li><b>Habit.<\/b> If we don’t change user habits, we’ll keep old stuff.<\/li>\n<\/ol>\n<ul>\n<li>Some people use the current feed the old way. We shouldn’t break their habit. Let’s add a history button. This is about the new way to access the feed. Don’t show it for a long time. If the user opens the feed, we’ll remove the button.<\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i4.jpg\" width=\"2541\" height=\"1833\" alt=\"\" \/>\n<\/div>\n<ol start=\"5\">\n<li><b>Additional entry points.<\/b> Finding more entry points will increase availability.<\/li>\n<\/ol>\n<ul>\n<li>When we spoke with users we found something interesting. When people contact the support team (chat) they go to watch stories on the home screen because they’re afraid to close the app (in general!!!). We must find a way to deal with these situations. This could affect how accessible the feed is.<\/li>\n<\/ul>\n<ul>\n<li>We knew this idea wouldn’t make it into the first version, so we didn’t make a prototype. But you can imagine it in your mind.<\/li>\n<\/ul>\n<h2>Priority<\/h2>\n<p>I met with the product manager and engineers to estimate the hypotheses according to two parameters: business value and technical complexity. We made a list of priorities.<\/p>\n<ol start=\"1\">\n<li><b>Main screen.<\/b> Adding the feed to the home screen will make it easier to access and more likely to be used.<\/li>\n<\/ol>\n<ul>\n<li>∞ ⁄ 5 = ∞<\/li>\n<\/ul>\n<ol start=\"2\">\n<li><b>Interest.<\/b> Make an entry point interesting to increase its open and retention rate.<\/li>\n<\/ol>\n<ul>\n<li>3 ⁄1 = 3<\/li>\n<\/ul>\n<ol start=\"3\">\n<li><b>Clear.<\/b> Make the opening of the feed simple and clear to increase accessibility.<\/li>\n<\/ol>\n<ul>\n<li>3\/1 = 3<\/li>\n<\/ul>\n<ol start=\"4\">\n<li><b>Habit.<\/b> If we don’t change user habits, we’ll keep old stuff.<\/li>\n<\/ol>\n<ul>\n<li>3 ⁄ 2 = 1.5<\/li>\n<\/ul>\n<ol start=\"5\">\n<li><b>Additional entry points.<\/b> Finding more entry points will increase availability.<\/li>\n<\/ol>\n<ul>\n<li>4 ⁄ 4 = 1<\/li>\n<\/ul>\n<h2>Scoping<\/h2>\n<p>We break down our ideas into iterations to get the product to users quickly and make sure it’s perfect.<\/p>\n<p><i>Iteration 1<\/i><\/p>\n<ul>\n<li><b>Main screen.<\/b> If we make the feed on the home screen, it will increase its accessibility and retention rate. This is our main idea, we will  make it.<\/li>\n<li><b>Interest.<\/b> Make an entry point interesting to increase its open and retention rate. I really want to do it at once, so that it will be the cherry on the cake. But if we don’t have time, we’ll put it in a separate iteration. Of course, it will be an ab-test to understand the impact of this particular idea.<\/li>\n<\/ul>\n<p><i>Next iterations<\/i><\/p>\n<ul>\n<li><b>Clear.<\/b> Make the opening of the feed simple and clear to increase accessibility. Let’s test it separately, in case this problem doesn’t exist and it is clear and simple without some additional activities.<\/li>\n<li><b>Habit.<\/b> If we don’t change user habits, we’ll keep old stuff. Important stuff. But we’ll run the first iteration only for new users and if everything is good there, we’ll make this idea and publish an update for everyone.<\/li>\n<li><b>Additional entry points.<\/b> Finding more entry points will increase availability. Oh, it’s definitely a contender to make it out of the first round!<\/li>\n<\/ul>\n<p>— Let’s go!<\/p>\n<h2>Iteration 1 · hi-fi<\/h2>\n<p>I just wanted to point out that our lo-fi prototypes already sounded pretty hi-fi. Having said that, we didn’t come across any major technical issues. So, all the ideas from the concepts made it through to the hi-fi stage, which is pretty unusual.<\/p>\n<p>But the final solution was this. The feed on the main screen looks like a top sheet that you can open by swiping from the top to the bottom. Plus, we made it so you can just click on the dragger and text to open it. We figured this out during the UX tests, but we assumed it in advance.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-new.jpg\" width=\"2541\" height=\"2031\" alt=\"\" \/>\n<\/div>\n<p>Above the dragger is a shortened descriptor from the feed, which changes every day along with the full descriptor inside the feed. You can read about this in the case study about <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/news-card\/\">the news card.<\/a><\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-new2.jpg\" width=\"2541\" height=\"1860\" alt=\"\" \/>\n<\/div>\n<p>Just then, Sergei Egorov came along. The second designer to join us. I needed to move on to other things. Sergei took the reins as the second designer on the project. The second half of the work on the final layouts is creating animations of opening and closing the feed. Based on my prototype, Sergei put together a much more detailed one with a description of all the details.<\/p>\n<p>To close the feed, just hit the close button or swipe down. When we were testing it out, we realised that we needed to make closing by swiping up, so that it’s the reverse of opening. This meant there were three ways to close the feed in total. This way, everyone would know how it worked.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-new3.jpg\" width=\"2541\" height=\"2031\" alt=\"\" \/>\n<\/div>\n<p>We had to get the most complex interactive feature in the Tinkoff app up and running at the time, which was a big challenge for the whole team. It was pretty straightforward to develop the animation and the feed itself on Android, but we hit a few snags on iOS. But we managed to get around all those limitations in the end. Sometimes we had to switch up our strategy and come up with quick fixes, so Sergei spent a lot of evenings with the engineers. Sergei says,<\/p>\n<ul>\n<li><i>“We often sat with the engineers late into the night tweaking details and catching endless bugs together. I even picked up a few lines of code in Xcode.”<\/i><\/li>\n<\/ul>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-serg.jpg\" width=\"2541\" height=\"1992\" alt=\"\" \/>\n<\/div>\n<p>At some point, we got everything to a state that could be called a release state. And it was so lovely to see that happen!<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/feedmain.jpg\" width=\"2560\" height=\"1918\" alt=\"\" \/>\n<\/div>\n<h2>First launch and results<\/h2>\n<p>We released it as an AB test for a new audience. At the same time, we ran a separate AB test on the description. Here’s what we found out.<\/p>\n<ol start=\"1\">\n<li>We saw a big jump in the number of people who stuck around and checked out the feed on a weekly basis (1-week feed retention rate).<\/li>\n<li>The percentage of users accessing the feed on the app shot up several times. This indicator saw a nice increase, even if it couldn’t help but grow.<\/li>\n<li>The engagement rate of the feed saw a slight decrease. This is because more people are now entering the feed, but the quality of these users has dropped. They’re not as active as they could be. We’ll be addressing this in the next episodes.<\/li>\n<li>There was no change to the weekly retention rate of the app, statistically speaking. We were disappointed, but not overly so. It’s really difficult to make changes.<\/li>\n<li>The descriptor did the job. Without it, the retention and open rates in the feed were lower.<\/li>\n<\/ol>\n<p>I’m happy to say that we met our goals, and we’re all proud of that.<\/p>\n<h2>Role and platforms<\/h2>\n<ul>\n<li>I participated in the formulation and confirmation of the problem together with the product manager.<\/li>\n<li>I did the primary research.<\/li>\n<li>I formulated hypotheses and participated in prioritization together with the product manager and engineers.<\/li>\n<li>Together with the manager, we divided all the hypotheses into iterations.<\/li>\n<li>I designed lo-fi and and first part of hi-fi mockups and described the requirements together with the technologists and engineers.<\/li>\n<\/ul>\n<p>Half of the layouts and animations were designed by Sergei Egorov. He joined us in the middle of the project as the second designer. Sergei helped QA engineers to run all the flow and described bugs.<\/p>\n<p>Basically, all solutions work on android and iOS.<\/p>\n<h2>Reflection<\/h2>\n<p>I think the first version of the personal feed opening could have been made much simpler, but it’s great that we overestimated the requirement at the start and made the transition above the level of the traditional design approach in the company. I’m really proud of this little project. See you in the next episodes, thank you!<\/p>\n<h2><a href=\"https:\/\/telegra.ph\/Kak-my-zatashchili-personalnuyu-lentu-na-glavnyj-ehkran-mobilnogo-banka-i-povysili-metriki-v-3-raza-04-13\">Story about the same, but from Sergei, only in Russian<\/a><\/h2>\n",
            "date_published": "2024-08-26T22:36:06+00:00",
            "date_modified": "2024-10-01T15:07:17+00:00",
            "image": "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-audience-dia-2.jpg",
            "_date_published_rfc2822": "Mon, 26 Aug 2024 22:36:06 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "193",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-audience-dia-2.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/feedmain.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-old.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-audience-dia-3.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-2.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i1.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i1-1.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i1-2.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i1-3.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i1-4.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i1-5.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i2.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i3.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-i4.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-new.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-new2.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-new3.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-feed-serg.jpg"
                ]
            }
        },
        {
            "id": "191",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/comments\/",
            "title": "Comments in stories",
            "content_html": "<p>I’d like to share a story about how we made a comments in stories. By doing so, we increased the number of stories read and the number of days in stories by 13%. I won’t describe the case in detail here, as it is described in <a href=\"https:\/\/telegra.ph\/Kak-my-vstroili-kommenty-v-istorii-mobilnogo-banka-Tinkoff-07-27\">great detail by Misha,<\/a> I will only share a few points.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-comments.jpg\" width=\"2560\" height=\"1796\" alt=\"\" \/>\n<\/div>\n<p>Tinkoff is an online ecosystem or super app based on financial and lifestyle services. The best mobile privetely-held bank in the world according to Global Finance. The third largest bank in the CIS with 30,000,000 customers.<\/p>\n<h2>Situation and challenge<\/h2>\n<p>We need to sell financial products in some way, this is the company’s main income. In order to do this more effectively, we talk about financial products in stories. Consequently, engagement in these stories has a positive effect on sales. That’s why we decided to make a comments module as a tool for engaging in our stories. At the same time, we conducted research and made sure that people want to be involved in the community, to share their opinions, to ask questions.<\/p>\n<h2>Actions<\/h2>\n<p>We did a simple discovery. Analyzed similar products, analyzed similar solutions within Tinkoff and did a desk study of benchmarks. In the end we have 6 hypotheses, prioritized them and took the first two hypotheses in the first iteration to cover all success criteria. As part of the first iteration, made hi-fi mockups and tested them. I’m not talking about a dozen approaches, how the comments could look like, it’s all <a href=\"https:\/\/telegra.ph\/Kak-my-vstroili-kommenty-v-istorii-mobilnogo-banka-Tinkoff-07-27\">described in detail by Misha.<\/a><\/p>\n<h2>Results<\/h2>\n<p>At the beginning of September we launched AB test. A few weeks later, we go into analytics, and the number of comments there has increased 70 times in relation to the previous weeks. What is the reason? Comments were enabled on Junior users (kids under 14). They made this feature monumental.<\/p>\n<p><b>Total number of stories read increased by 12.9% and number of days by 13.2%<\/b><\/p>\n<p>And these are the results of adult clients, in children it is 2-3 times higher, but we don’t include children in the results for obvious reasons. The role of designer was performed by Misha Naer. I played the role of the head of the design process. And these are the results of the first iteration, further on it will be more interesting. See you in the next episodes, thank you!<\/p>\n",
            "date_published": "2023-09-04T21:53:32+00:00",
            "date_modified": "2023-09-12T23:25:52+00:00",
            "image": "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-comments.jpg",
            "_date_published_rfc2822": "Mon, 04 Sep 2023 21:53:32 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "191",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [],
                "og_images": [
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-comments.jpg"
                ]
            }
        },
        {
            "id": "185",
            "url": "http:\/\/www.ivanzviahin.by\/blog\/all\/news-card\/",
            "title": "News card in personal feed · Tinkoff",
            "content_html": "<p>How we made a news card in the feed and increased CTR of first card by 32%, 1-week retention rate of the feed by 8%, open rate by 4% and engagement rate by 35%.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-new-sexy-feed.jpg\" width=\"2560\" height=\"2005\" alt=\"\" \/>\n<\/div>\n<p><a href=\"https:\/\/apps.apple.com\/RU\/app\/id455652438\">Tinkoff<\/a> is an online ecosystem or super app based on financial and lifestyle services. The best mobile privetely-held bank in the world according to Global Finance. The third largest bank in the CIS with 30,000,000 customers.<\/p>\n<p>A personal feed is a product. With the help of which we are building a communication platform where people learn all about finance, save money and have fun. Businesses need a personal feed to sell financial products through it. Users need to have fun, learn something new, be part of an expert community. In simple words, it’s just a feed of events and news.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-old-feed.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<h2>Problem for users<\/h2>\n<p>Analyzing different types of cards and collections, we noticed an increase in interest in news cards, especially when we combine them into collections. Based on this insight, we decided that we need to develop in this direction.<\/p>\n<p>Hence the problem — people want to be able to see an up-to-date selection of news based on their interests. They don’t want to collect this news in different places, they want to see it all at once. Most importantly, this was confirmed in a series of user interviews that were aimed at finding the answer “Why do users use the feed?”<\/p>\n<p>We decided that it needed to be checked somehow cheaply. And we collected a selection of news based on the type of card already available.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-with-news-old-card.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<p>After such an experiment, we noticed a significant increase (+24%) in the CTR of this card relative to the most popular card in this place. So we realized that we need to improve the user experience of this card and come up with maximum ways to engage a person.<\/p>\n<h2>Problem for business<\/h2>\n<p>We are always looking for ways to increase CTR with the feed cards. Because with the growth of CTR → engagement grows. With the growth of engagement, the loyalty of users grows, and with the growth of loyalty, the revenue from sales of our internal services grows.<\/p>\n<h2>Audience<\/h2>\n<p>The audience is very wide and diverse. But we aimed at all our bank users with an active lifestyle. I can’t share the audience of the personal feed, but it makes up the majority of the total number of customers. Considering that we have 30,000,000 customers, the scale of the product is confirmed. Wow!<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-audience-dia.jpg\" width=\"2541\" height=\"528\" alt=\"\" \/>\n<\/div>\n<h2>Success criteria<\/h2>\n<p>We will consider the success criterion to be CTR of this card, which will be higher than CTR of the news card from the experiment above (which means it will be higher than any other card in the first place of the feed).<\/p>\n<p>Additionally, we will look at the open and 1-week retention rate of the feed, because the first card will be visible in a hidden state.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-compare-was-willbe.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<h2>Discovery · Interview<\/h2>\n<p>Fortunately, quite by chance, we conducted a series of interviews with our users in parallel. We were trying to find an answer to the question of why users read the feed. We had a small product market fit, but we didn’t understand exactly why it happened.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-interview.jpg\" width=\"2526\" height=\"1551\" alt=\"\" \/>\n<\/div>\n<p>Total 19 in-depth interviews. The latest news got into the top 3 insights. This confirms our initial insight. In addition, we realized that we need to recommend news in a personalized format and give only a selection of headlines.<\/p>\n<h2>Discovery · Analysis of similar products<\/h2>\n<p>Next, we went to see how different products aggregate different information into a card. Here we found some interesting ideas.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-similar-products.jpg\" width=\"2526\" height=\"1413\" alt=\"\" \/>\n<\/div>\n<p>First, almost all cards with no more than four lines of content. If more, then do a horizontal scroll. Secondly, it is important to understand the date of publication, how new the material is. Third, currency exchange rates and investment stickers look cool together with a selection of news as a single widget. Fourth, the introductory description, as an engagement tool, creates the effect of personalization. Additionally a personal address by name attracts a lot of attention. (everyone already knows that)<\/p>\n<h2>Wow! As a result, we had a lot of ideas. We have described them in the form of hypotheses below<\/h2>\n<h2>Hypothesis formulation and low-fi prototypes<\/h2>\n<p>Now the card is colored and we know that this is important. When the feed is hidden, a piece of the card is visible and it attracts attention. We decided not to experiment with this and further considered it only in color.<\/p>\n<ol start=\"1\">\n<li><b>Dates.<\/b> If we display the publication dates of articles, it may affect card CTR.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/lofi-dates.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<ol start=\"2\">\n<li><b>Pictures.<\/b> If we add pictures to the news, it may affect card CTR.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/lofi-pic.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<ol start=\"3\">\n<li><b>Personalisation.<\/b> If we display news based on user interests, it may affect CTR and retention rate.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/lofi-pers.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<ol start=\"4\">\n<li><b>Name.<\/b> If we contact to you personally, it may affect feed open rate.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/lofi-name.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<ol start=\"5\">\n<li><b>Introductory text.<\/b> If we write a humorous introductory text, it may affect retention rate.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/lofi-text.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<ol start=\"6\">\n<li><b>Currency rates.<\/b> If we display currency rates and share price, it may affect retention rate.<\/li>\n<\/ol>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/lofi-rates.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<h2>Priority<\/h2>\n<p>I set up a meeting with the product manager and engineers to estimate all hypotheses according to two parameters: technical complexity of the implementation (from 1 to 5) and business value (from 1 to 5). We divided one into the other and got an hi-level prioritisation coefficient. So...<\/p>\n<p><i>Card CTR <\/i><\/p>\n<ul>\n<li><b>Dates.<\/b> If we display the publication dates of articles, it may affect card CTR.<br \/>\n3 ⁄ 1 = 3<\/li>\n<li><b>Pictures.<\/b> If we add pictures to the news, it may affect card CTR.<br \/>\n3 ⁄ 1 = 3<\/li>\n<li><b>Personalisation.<\/b> If we display news based on user interests, it may affect card CTR and retention rate.<br \/>\n5 ⁄ 5 = 1<\/li>\n<\/ul>\n<p><i>Open rate<\/i><\/p>\n<ul>\n<li><b>Name.<\/b> If we contact to you personally, it may affect open rate.<br \/>\n3 ⁄ 1 = 3<\/li>\n<\/ul>\n<p><i>Retention rate<\/i><\/p>\n<ul>\n<li><b>Introductory text.<\/b> If we write a humorous introductory text, it may affect retention rate.<br \/>\n3 ⁄ 2 = 1.5<\/li>\n<li><b>Currency rates.<\/b> If we display currency rates and share price, it may affect retention rate.<br \/>\n2 ⁄ 2 = 1<\/li>\n<\/ul>\n<h2>Scoping<\/h2>\n<p>We divide all into iterations in order to deliver a valuable product as quickly as possible. We focus on three metrics card CTR, retention rate and feed open rate. Therefore, we can take one hypothesis for each metric in each iteration. Of course, we understood that they could influence each other, but speed is more important.<\/p>\n<p><i>Iteration 1<\/i><br \/>\nWe definitely make a news card with dates right away. We had a dispute about the pictures, the product manager believed that it would work better without pictures. We agreed on an AB test. Additionally, we will take the appeal by name, since it affects another metric.  We do not take hypotheses aimed at retention rate in the first iteration due to the fact that they are complex, and we want to deliver value as early as possible.<\/p>\n<ul>\n<li><b>Dates.<\/b> If we display the publication dates of articles, it may affect card CTR.<\/li>\n<li><b>Pictures.<\/b> If we add pictures to the news, it may affect card CTR.<\/li>\n<li><b>Name.<\/b> If we contact to you personally, it may affect open rate.<\/li>\n<\/ul>\n<p><i>Iteration 2<\/i><br \/>\nThe text-introduction will be launched separately. Potentially, this can affect the retention rate individually, it is interesting to check.<\/p>\n<ul>\n<li><b>Introductory text.<\/b> If we write a humorous introductory text, it may affect retention rate.<\/li>\n<\/ul>\n<p><i>Iteration 3<\/i><br \/>\nAfter that, we will add a widget with currency rates and investment tickers. It is also interesting to test them separately because this hypothesis is also aimed at the retention rate.<\/p>\n<ul>\n<li><b>Currency rates.<\/b> If we display currency rates and share price, it may affect retention rate.<\/li>\n<\/ul>\n<p><i>Iteration 4<\/i><br \/>\nNext, we try to personalize the news (a difficult thing), so in the end.<\/p>\n<ul>\n<li><b>Personalisation.<\/b> If we display news based on user interests, it may affect CTR and retention.<\/li>\n<\/ul>\n<p>— Let’s go!<\/p>\n<h2>Iteration 1 · hi-fi<\/h2>\n<p>We added only 4 news, it seems enough to start and looks easy. We tried to make the interface as simple as possible, we have already made mistakes with this many times in the collections. And there was an insight from users that they want to see all the current news in a list at once. We borrowed the algorithm from a web magazine, it is already ready there, current news.<\/p>\n<p>We had two options:<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-1-news.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<p>I chose the second option. It looks simpler and more aesthetically pleasing. Next...<\/p>\n<p>Added dates. There are not too many options for how this can be shown, so we made it as simple as possible. We already have a date display style in other cards.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-1-datesandrules.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<p>We enter the dates according to special rules that I have formed.<\/p>\n<div class=\"e2-text-table\">\n<table cellpadding=\"0\" cellspacing=\"0\" border=\"0\">\n<tr>\n<td><b>Have<\/b><\/td>\n<td><b>Show<\/b><\/td>\n<\/tr>\n<tr>\n<td>≤ 5 min<\/td>\n<td>just now<\/td>\n<\/tr>\n<tr>\n<td>< 1 hour<\/td>\n<td>56 min ago<\/td>\n<\/tr>\n<tr>\n<td>< 2 hours<\/td>\n<td>1 hour ago<\/td>\n<\/tr>\n<tr>\n<td>< 1 day<\/td>\n<td>23 hours ago<\/td>\n<\/tr>\n<tr>\n<td>< 2 days<\/td>\n<td>yesterday<\/td>\n<\/tr>\n<tr>\n<td>< 8 days<\/td>\n<td>6 days ago<\/td>\n<\/tr>\n<tr>\n<td>≥ 8 days<\/td>\n<td>18 february<\/td>\n<\/tr>\n<tr>\n<td>≥ 1 year<\/td>\n<td>18 february 2020<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<p>Added an appeal by name. I made it as simple as possible, using the available styles from other cards. That’s where we stopped.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-1-name.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<p>Added pictures. As I said before, we had disagreements on this, so it got into the first iteration, we will run them AB test. Option A without pictures, option B with pictures. We will show the card 50-50, we will look at the card CTR.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-1-abpics.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<p>That is all.<\/p>\n<p>We didn’t do any interface tests, because it seems to us that there is nothing to check here. I checked only the list of <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/self-checking-the-interface\/\">self-checking the interface.<\/a> So, it was → will be.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-1-willbe.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<h2>First launch and results<\/h2>\n<p>AB test results. At the first visit, users tap better on the news card without pictures. The relative uplift in CTR is 9%. It does not affect taps when re-entering. It does not affect the return to the feed. The card without pictures won, I cried :-(<\/p>\n<p>In general, first card CTR +8% (new format and dates) and feed open rate +4% (address by name). Cool! Let’s move on to the next iterations.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-role-3.jpg\" width=\"2526\" height=\"1527\" alt=\"\" \/>\n<div class=\"e2-text-caption\">This is a product manager, his name is Nikita. Nikita is glad that he won the AB test. He was for the option without pictures<\/div>\n<\/div>\n<p>Moving on!<\/p>\n<h2>Iteration 2 · hi-fi<\/h2>\n<p>Hello again! It’s time to work with the retention rate as part of the news card and we have an introductory text on this. The main idea is that we want to make an introductory text that will change every day. It should have a welcoming meaning.<\/p>\n<p>We strongly believe that the text should be humorous, this was confirmed in user interviews, people want something entertaining, a lot of sad things are happening in the world anyway. This can be a great reward for action.<\/p>\n<p>We have not found an editor resource that will write an introductory text every day for several days ahead. So I came up with and wrote them myself. I really want to test this.<\/p>\n<p>What might it look like? We didn’t want to come up with something new (so as not to complicate the idea of test) yet, so we took the text style from other cards as a basis and applied it in our news card. The main thing is that it should be readable, simple and understandable. We have reduced the number of articles to make it look easier visually. We removed the “current news” descriptor and moved it inside the introductory text to make it all look easier.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-2-text.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<p>An important learn that we found. We are well aware that it is ideal to use the hook model for the retention rate boost. And we even figured out how to do it. The reason is the position of the feed in the app and the policy of contacts to send push messages. We promised ourselves to try it after moving the feed to a more accessible place in the app. But about this in another story.<\/p>\n<p>While we design a text, another idea came up. What if we ask some interesting question in the introductory text, and somewhere in the middle of the feed we give an answer in the form of a story card. If we use the story card, we won’t need to develop anything additionally – perfect for the test. It seems that in addition to the retention rate, we can influence the engagement rate of the feed.<\/p>\n<p><b>feed engagement rate = (user tap + like + bookmark + share + swipe) \/ all users × 100%<\/b><\/p>\n<p>The idea should work because people will look for an answer, react to it and get involved in other content. Sounds interesting?<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-2-story.jpg\" width=\"2526\" height=\"1776\" alt=\"\" \/>\n<\/div>\n<p>Sure! Sounds interesting. So, it was and will be. Of course, guys, we started with an AB test to understand the impact of the second iteration on the result.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-2-willbe.jpg\" width=\"2526\" height=\"1731\" alt=\"\" \/>\n<\/div>\n<h2>Second launch and results<\/h2>\n<p>In general, feed 1-week retention rate +8% (introductory text with a question and answer) and feed engagement rate +35% (introductory text with a question and answer). It’s hard to understand why it affected engagement so much, but I like it. The test did not affect the CTR of the first card and the open rate in any way, which is also important.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-2it.jpg\" width=\"2541\" height=\"528\" alt=\"\" \/>\n<\/div>\n<h2>Iteration 3 and 4 · not done<\/h2>\n<p>An interesting thing happened, we decided to redo the concept of the feed as a whole and separate the news selection from the text and the address by name. The introductory text and the appeal should become part of the feed itself and be independent, but that’s another story.<\/p>\n<p>So, we have postponed working with currency exchange rates and personalisation. But I want to show you the layouts and developments on these tasks, they should not be lost. We will return to them later, but in another story.<\/p>\n<div class=\"e2-text-picture\">\n<img src=\"http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-34.jpg\" width=\"2526\" height=\"1695\" alt=\"\" \/>\n<\/div>\n<h2>Role and platforms<\/h2>\n<p>I participated in the formulation and confirmation of the problem together with the product manager. I communicated with analysts to find out insides. I participated in user interviews and analysis of similar products. The research team helped me a lot, thanks to them.<\/p>\n<p>I formulated hypotheses and participated in prioritization together with the product manager and engineers. Together with the manager, we divided all the hypotheses into iterations. I designed lo-fi and hi-fi mockups and described the requirements together with the technologists and engineers. I helped QA engineers to run all the flow and described bugs. I wrote dozens of introductory texts for the news card. Basically, all solutions work on android and iOS.<\/p>\n<h2>Reflection and final results<\/h2>\n<p>Although the results cannot be called super-high, but they can be called real.<br \/>\nWe achieved:<\/p>\n<ul>\n<li>first card CTR without development +24%<\/li>\n<li>first card CTR with development +8%<\/li>\n<li>feed open rate +4%<\/li>\n<li>feed 1-week retention rate +8%<\/li>\n<li>feed engagement rate +35%<\/li>\n<\/ul>\n<p>I would certainly like more. Unfortunately, we couldn’t do all the planned iterations, but it was influenced by external factors. Plus, in the second iteration, it was hard for me to throw out the subscription model. But we understood that it was too early to give such functionality, the card does not take into account interests.<\/p>\n<p>The story looks real and confirms the theory of <a href=\"https:\/\/ivanzviahin.by\/blog\/all\/process-story\/\">my design process,<\/a> which works in practice. Next time we’ll try to do more iterations. See you in the next episodes, thank you!<\/p>\n<p>Here I’m telling the same story, only live:<\/p>\n<div class=\"e2-text-video\">\n<iframe src=\"https:\/\/www.youtube.com\/embed\/Brz_XeX-wAQ?enablejsapi=1\" allow=\"autoplay\" frameborder=\"0\" allowfullscreen><\/iframe>\n<div class=\"e2-text-caption\">Don’t forget to turn on the subtitles, this presentation is in English and I’m speaking in my native language<\/div>\n<\/div>\n",
            "date_published": "2023-03-21T20:31:00+00:00",
            "date_modified": "2024-07-18T22:34:26+00:00",
            "image": "http:\/\/www.ivanzviahin.by\/blog\/pictures\/lofi-color.jpg",
            "_date_published_rfc2822": "Tue, 21 Mar 2023 20:31:00 +0000",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "185",
            "_rss_enclosures": [],
            "_e2_data": {
                "is_favourite": true,
                "links_required": [
                    "system\/library\/jquery\/jquery.js",
                    "system\/library\/media-seek\/media-seek.js"
                ],
                "og_images": [
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/lofi-color.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-1-platforms-2.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-new-sexy-feed.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-old-feed.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-with-news-old-card.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-audience-dia.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-compare-was-willbe.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-interview.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-similar-products.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/lofi-dates.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/lofi-pic.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/lofi-pers.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/lofi-name.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/lofi-text.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/lofi-rates.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-1-news.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-1-datesandrules.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-1-name.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-1-abpics.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-1-willbe.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-role-3.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-2-text.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-2-story.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-2-willbe.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-2it.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/pic-34.jpg",
                    "http:\/\/www.ivanzviahin.by\/blog\/pictures\/remote\/youtube-Brz_XeX-wAQ-cover.jpg"
                ]
            }
        }
    ],
    "_e2_version": 3849,
    "_e2_ua_string": "E2 (v3849; Aegea)"
}