Back to Explore
GuideVibeFix editorialUpdated Nov 20, 2026

Don’t Let the Follow Button Sit There: Follow and Follower Relationships in Your Vibe Project

Following is not a number but a relationship mechanism: three button states, follow requests for private accounts, recommendation boundaries, and dignified unfollows — a hands-on guide with a worked funnel.

A finger tapping the blue “Follow” button on a phone screen (real photo)

One thing up front: this guide is only about the follow relationship itself — following, being followed, unfollowing, follow recommendations, and follow requests for private accounts. How the activity feed is ranked and how feed cards are built belongs to the earlier Activity Feed guide and is not repeated here; reporting, blocking, and muting — the ways to break a relationship — have their own guide too, and only come up at the end where they meet following. The example product in this article, “Qinghe Notes” (a journal-sharing community), and the people in it, “A-Li” and “Old Zhou,” are fictional examples used to make the points concrete — not a real product or real users.

Many vibe projects add a follow feature as an afterthought. They see other products with follower counts, decide they should have one too, put a “Follow” button on the profile page next to a number, and call it done. Three months later the follower count is stuck in double digits, the button barely gets clicked, and the author starts wondering whether the product needs social features at all. The problem is usually not “whether” but “how.” A follow button is not a decoration; it is a relationship mechanism. You have to work out who follows whom, what following gets you, and what happens when a follow ends. Until those three things are clear, the button is just sitting there.

1. Does your product even need following?

Do not start with “where does the button go.” Start with “what changes after someone follows.” If nothing changes — the home page is the same, the notifications are the same — why would anyone tap it? Following only works when it changes what a user sees the next time they open the product. There are three common shapes where it works. The first is creator-led: you follow a person so you do not miss their new work. Journal communities, writing platforms, and art-sharing sites all fit here, and the value is obvious. The second is collaboration-led: you follow a person to make working together easier — a teammate, a project author — so that direct messages, mentions, and collaboration invites are one tap away. The third is commerce-led: you follow a shop or a seller to hear about new stock, price drops, and restocks first. The button copy, placement, and follow-up are different in each shape. Creator-led products put the follow button in the most visible spot on the author page; collaboration-led ones treat following as a light action, like adding a frequent contact; commerce-led ones bundle following with a “new arrival alert” so one tap buys two benefits.

Plenty of products do not need following at all. If yours is a tool — a ledger, a Pomodoro timer, a file converter — users open it to get a job done and leave. Following the author buys them nothing. Adding the feature anyway leaves an unclicked button on the screen and one more thing for new users to puzzle over: why would I follow the author of a ledger? The test is one sentence: “After following, what extra thing will the user see next time they open the product?” If you cannot write that sentence, do not add it. Add it later, when the product grows content or grows people. A follow feature added too early is worse than one added late — a button nobody uses makes the whole product look unmaintained.

There is also a subtler failure: the product is content-led, but nobody follows. Usually the payback of following was never explained. A user opens an author page, sees an avatar, a bio, and a row of works, and has no idea what following does. Will they get a reminder for new work, or just one more name in a list? Many products say nothing here and leave the user guessing. The fix is one line next to the button: “Follow, and you will be notified when they publish something new.” That single line turns a vague social gesture into a clear deal: you tap once, and I promise you will not miss anything. In our fictional example, “Qinghe Notes” put exactly that line under the follow button on A-Li’s page, and the click rate went up — the numbers in that story are invented, but the principle is real, so do not quote the numbers.

2. The follow button: three states, copy, and placement

The button looks simple, but it has several states. The basics are three: not following shows “Follow,” following shows “Following,” and a mutual follow shows “Friends” or “Following each other.” The three states must be tellable at a glance — change at least two of color, copy, and icon. The most common mistake is changing only the copy and not the color, so the user stares at the button wondering whether the tap worked. Do this instead: an un-followed state in a solid primary color, a followed state as an outlined or gray button, and a mutual state with a two-way arrow icon and different copy. The button must change the instant it is tapped, with a light toast such as “You are now following A-Li,” and only revert if the request fails — with a “Follow failed, please try again” message. Optimistic first, verify after; that is what makes a button feel alive.

Placement matters too. Next to the avatar on the profile page is the most common spot, but not the only one. The author row on a work detail page, next to an author’s name in the comments, and the author row in search results can all carry a follow button. The rule is: the button should be at hand the moment the user thinks “I want to follow this person.” A user who just finished a good journal entry on the detail page is already warm; making them open the profile to find the button lets that impulse cool by half. A small follow button in the author row of the detail page often converts better than the big one on the profile. But do not stuff a big button into every author row in a list — a screen full of follow buttons reads like a sales pitch. Small outlined buttons in lists, big solid buttons on profiles: keep the roles clear.

Keep the copy plain. “Follow,” “Following,” “Friends” — that is enough. Do not write “Become a fan,” “Join my circle,” or “Be my friend.” The user is tapping a feature button, not making a confession. Unfollow copy needs the same care: the confirmation after tapping “Following” should just say “Unfollow A-Li?” — not “A-Li will be sad.” Unfollowing is a normal action; make it dignified and the user may come back one day. Turn it into something shameful and the user will uninstall the product along with the guilt.

3. One-way follows or two-way friends?

This is the most foundational choice in the whole feature, and getting it wrong breaks everything downstream. A one-way follow means: I follow you, no approval needed, and you do not have to follow me back. Weibo, X, and Xiaohongshu work this way. It has a low bar, which suits content products. A two-way friendship means: I add you, you approve, and only then are we friends. WeChat and QQ work this way. It is more mutual and more private, which suits collaboration and close-circle products. Neither is better; only fit matters. The test is whether following someone lets you message them directly. If it does, one-way follows create a spam problem: any stranger who follows you can message you, and the inbox fills with ads. In that case either pick two-way friendship or put a gate on messages, such as “only mutual follows can message each other.”

Many vibe projects make the same mistake here: they copy the one-way follow button and the two-way friend messaging, mixing two models into one. The result is harassment complaints, and the author discovers the product never had a “who can message me” switch at all. The fix is to decide the permissions as a set, once the model is picked. In a one-way product the default should be “strangers cannot message, they can only comment,” or “stranger messages go to a requests inbox first.” In a two-way product the follow request itself is the gate, and the approve/reject flow has to be done properly. Do not treat these as “later” features: once harassment starts, users leave faster than you can ship fixes.

One hybrid is worth considering: one-way follows by default, but any author can flip a switch to make their account require approval to follow. That is the private account covered in the next section. It hands the choice to the user instead of the product deciding for everyone. Creators who want growth stay public; people who want quiet go private. The product offers both modes and does not decide for them.

4. Private accounts and follow requests

A private account does not hide the profile; it turns “follow” into “apply.” Once a user goes private, tapping Follow does not change the button to “Following” — it changes to “Requested,” and the account owner receives a follow request. Only after approval does the follow count, and only then can the requester see the content. A rejection should tell the requester “Your follow request was not approved,” not “You were rejected.” The wording gap is small; the feeling gap is large. The request list needs its own entry, separate from notifications. Notifications are glanced at and gone; requests are decisions to make. Mix them together and requests drown in likes and comments, unanswered for three days, by which time the requester has forgotten all about it.

Follow requests suffer most from being left on read. The requester waits three days with no reply, not knowing whether the owner never saw it, is still thinking, or rejected it without the system saying so. The fix is an explicit state machine: pending, approved, rejected, expired. If a request sits pending for more than seven days, the system can nudge the owner once — “You have 3 follow requests waiting” — but no more than once a week. A rejected request should not keep reappearing for the requester; one rejection is enough. Should the requester be allowed to apply again? Yes, but with a gap — no re-application within thirty days of a rejection — so nobody can use requests to harass someone. These details look fiddly, but they decide whether a private account feels like peace and quiet or one more chore.

One more thing people forget about private accounts: what happens to existing followers when an account goes private? The answer is nothing — existing followers keep seeing the content. Privacy blocks new people; it does not evict old ones. That rule belongs in the confirmation dialog when someone goes private: “After going private, your current followers can still see your content; only new follows need your approval.” Otherwise users will fear that going private chases away their old followers and never dare to switch it on. And a private account’s works should not appear in the public recommendation feed — that is basic consistency. If the user chose private and you still push their work to the whole site, the word “private” means nothing.

5. Follower and following lists: do not build an awkward roll call

Follower and following lists are the most neglected pages in the feature. Many products ship a bare list in reverse chronological order — avatar, name, a follow button — and stop there. But the two lists have different user intents. Someone opening “my followers” wants to know who is following them: any friends in there, any big names, any suspicious accounts? Someone opening “my following” wants to clean up: who stopped posting, who do I want to unfollow? Sort and act on that intent. Followers: mutual follows first, then most recent. Following: most recently active first, with a search box so the user can find the person they want to unfollow.

Row actions need thought too. Every row in the follower list should offer “Follow back” and “Remove follower.” Removing a follower is easy to forget and important to have: the user does not want to be followed by someone, but does not want to block them either — blocking is too heavy; removing is just right. After removal the other person gets no notification; they simply stop being a follower, and the next time they open the profile they see the button back at “Follow.” The action should be quiet — no notification, no extra dialogs beyond one confirmation. Every row in the following list should offer “Unfollow” and “Message,” with unfollow taking one confirmation and messaging only open to mutual follows. Both lists need pagination; do not load thousands of rows at once and make the user scroll until their thumb hurts while the phone runs out of memory.

How numbers are shown matters too. Below ten thousand, show the exact count; above it, round to the thousands, like “12.4K.” That is readability, not vanity — nobody counts a seven-digit string under an avatar. The rule must be the same for your own counts and other people’s; no double standards. More importantly, do not fake the numbers. Buying followers, padding counts, counting bots as followers — once discovered, the product’s credibility is gone. A small follower count is fine, as long as it is real.

6. Follow recommendations: good intentions that turn into spam

Recommendations are where follow features most often go wrong. Done well, they rescue new users: someone just registered, knows nobody, and the recommendation list helps them find the first people worth following. Done badly, they are harassment: import the address book and message every contact “your friend joined, come follow them,” and the user has offended their friends before they even understand what happened. The first iron rule is: never follow someone on the user’s behalf, and never notify someone on the user’s behalf, without the user knowing. Address-book import needs its own permission screen that says plainly, “We will use your contacts to find friends already using this product. We will not message them.” After finding friends, list them and let the user pick — never auto-follow. Auto-following decides for the user; the user who discovers they mysteriously follow dozens of people deletes the app instead of thanking you.

Recommendations usually come from three sources: address-book friends, shared follows, and similar interests. Address-book friends are the most accurate and the most sensitive — separate permission, separate explanation. Shared follows means “A-Li, whom you follow, also follows Old Zhou — you might like to meet Old Zhou,” and the reason should be shown, because users only trust a recommendation they can see the reason for. Similar interests come from what the user has read and liked — the reason can read “you both like journal layouts.” A recommendation without a reason just feels like the product guessing. Frequency needs a cap too: once after registration, then once a week. Do not pin “people you may know” to the top of the home page every day, and do not re-suggest someone the user marked “not interested” for thirty days.

Cold start is especially hard: a new product has few users, and the recommendation list keeps showing the same few faces. The fix is not to pad the numbers but to change the dimension: when users are few, recommend “the most active authors this week” instead of “people you may know.” The active-author list changes daily, so every visit brings something new. And give authors an opt-out: “do not show me in recommendations.” Some users simply do not want to be recommended or to grow followers. Respect that, and the product keeps all kinds of people.

Follow conversion funnel: 1000 people open the profile, 640 see the follow button and pause, 410 tap follow, 352 follow successfully, 148 become active engagers

7. From opening a profile to sticking around: a fictional funnel, balanced

The funnel below is fictional, included to make follow conversion countable. Suppose A-Li, an author on “Qinghe Notes,” gets 1,000 profile visits in a month. Of those, 640 people see the follow button and pause — the other 360 tapped in by mistake or left after glancing at one work. Of the 640, 410 tap the follow button, a 64% tap rate, which is high and says A-Li’s work is genuinely attractive. Of the 410 taps, 352 turn into successful follows; the other 58 fail — network problems, the account being private so the tap becomes a pending request, or the user tapping and immediately undoing it. Of the 352 new followers, 148 are still around after 7 days as active engagers — they liked, commented, or at least opened A-Li’s new work. 148 out of 1,000 is a 14.8% overall conversion rate. The absolute values do not matter; the point is where the problem sits. If the tap rate is low, the problem is the profile content and button copy. If taps fail to convert, the problem is private-account handling and network retries. If follows succeed but most unfollow within 7 days, the problem is that following bought nothing — no continuing content payback. Funnels exist to locate problems, not to show off.

Unfollowing deserves its own look. People usually unfollow not because they dislike you, but because nothing happened after they followed: no new-work reminders, or reminders that led to content they did not care for. Treat an unfollow as feedback, not betrayal. When someone unfollows, one optional question is enough — “Mind telling us why?” — with three options: “content was not for me,” “too few updates,” “too many reminders.” Not a ten-question survey; the user is already walking out the door and has no patience for forms. Read those three answers once a month and you will know where the follow system leaks. But the question must be skippable. Turning unfollowing into a mandatory quiz only makes people dislike you more.

One more number is worth watching: the mutual-follow rate. If a user’s followers are mostly mutual, their follows come from a circle of acquaintances and the product has not yet connected them with strangers. If the mutual rate is very low, they are a pure creator whose followers come for the content. Neither is good or bad; it tells you what kind of relationship network this is. The product can respond accordingly: circle-type users need groups and messaging more; creator-type users need work stats and new-follower alerts. Following is not a number; it is a network, and different network shapes need different things from the product.

8. Following is not permission to message: where harassment starts

The most common follow-related complaint is not about following; it is about the messages that follow it. Many products tie “follow” to “can message”: follow someone and you can message them. Creators’ inboxes then fill with ads, pick-ups, and promotions. The fix is to treat following and messaging as two separate permissions with separate switches. The recommended default: only mutual follows can message directly; one-way follow messages go to a requests inbox the recipient chooses to read. Do not badge the requests inbox with a red dot, or at most a faint one — otherwise it is no different from the main inbox. Authors should also be able to turn messaging off entirely and keep the comments as the public channel. That is not unfriendly; it is giving creators a quiet place to work.

Mute, block, and report are the three lines of defense behind following, and people often confuse them. Muting means: I do not want to see your content, but I am not cutting ties, and you will never know. It fits the “wrong content, decent person” case. Blocking means: I want no further contact — you cannot follow me, message me, or see my profile. Unfollowing means: I do not want to see your content anymore, but I am not stopping you from seeing mine. The three are a ladder of intensity, and the product should put them at different entry points instead of piling them into one “More” menu and making the user guess. Reporting is different again: it is not for expressing dislike, it is for flagging rule-breaking content. The report entry should ask what is being reported — adult content, ads, harassment, personal attacks — and let the user pick a category instead of facing a blank text box. The full playbook for reporting, blocking, and muting has its own guide; the one point that matters here is that every way of breaking a follow should be quiet, dignified, and reversible — except reporting, which is about rule-breaking.

There is also a boundary around minors and privacy. Should follower and following lists be public by default? The recommendation: public by default, but with a switch for “do not show my following list.” Some users do not want others to know whom they follow, and that is a reasonable privacy need. Follower counts can be public; following lists do not have to be. And should a follow notify the other person? Yes — “someone followed you” is basic social courtesy. An unfollow should not notify anyone; quietly unfollowing is the user’s right. A follow request approval should notify; a rejection should not. These rules look small, but they decide whether users make friends in your product feeling relaxed or feeling watched.

9. Before launch, check this list

One, is the model decided — one-way or two-way — with messaging permissions settled as a set? Two, are the three button states tellable at a glance, changing instantly on tap and reverting with an explanation on failure? Three, does the private-account request flow work — pending, approved, rejected, and expired, each with its own copy? Four, can the follower and following lists be searched and paged, with remove-follower and unfollow entries? Five, do recommendations ever follow someone or notify someone without the user knowing? Six, is unfollowing quiet — no notification, no guilt trip, an optional reason at most? Seven, are following and messaging separated — do stranger messages hit a requests inbox first? Eight, are the numbers real — no padding, rounded to thousands above ten thousand? Nine, are the notification rules right — follow notifies, unfollow does not, rejection does not? Ten, are the switches all there — can users turn off messages, hide their following list, and opt out of recommendations?

Tick all ten and the follow feature is ready to ship. One last honest word: the launch bar for following is not “the button can be tapped” but “the relationship can be kept.” The moment a user taps Follow, the product’s promise has only just begun: you told them that next time they open the product, they will see this person’s new work. Whether that promise holds depends not on the button but on the content, the reminders, and the relationship care behind it. Keep the promise and follower counts grow on their own; break it and the prettiest button is still a decoration. Start with the smallest loop: one author, one follow button, one line saying “you will be notified of new work,” and one reminder delivered on time. Once that loop works, add recommendations, then private accounts, then the follower lists. Following is a relationship mechanism, not a feature checklist to ship in one go. Growing it slowly beats piling it all in at once.

Views 9Comments 0

Comments (0)

ME
0/1000
Loading comments...
Browse projectsPublish your project

Related articles

Real photo: a laptop, tablet, and phone on a wooden table showing the same green-leaf website, the phone view with navigation in one column, a potted plant nearby
Guide
Squashed on phones? Responsive layout and media queries, explained plainly

One page should stand up on a phone, a tablet, and a computer. This guide follows MDN's Responsive web design, Using media queries, and the viewport meta reference: fluid HTML, the viewport tag, fluid grids and max-width, images that never burst their container, media query syntax, breakpoints set by content, mobile first, responsive type, testing capability instead of width, and a pre-launch checklist.

Mobile AppsDesign ExperienceFrontend Engineering
Real photo: a bank of light gray metal filing cabinets with one drawer pulled open, revealing rows of hanging file folders inside
Guide
A real database inside the browser: IndexedDB local storage, explained plainly

localStorage only stores strings and has no indexes. IndexedDB is a real database in the browser: structured data, far larger capacity, indexes, and transactions. Following MDN's Using IndexedDB, IDBDatabase, and IDBObjectStore: the five-step routine, opening, upgrades, keys, indexes, transactions, add versus put, get, cursors, ranges, and multi-tab upgrades.

Tool TipsData WorkflowsFrontend Engineering
Real photo: hands typing on a MacBook Pro showing JavaScript code that changes HTML content, with a white mouse, papers, and binders on a white desk
Guide
Functions without the confusion: JavaScript functions, parameters, and arrow functions, explained plainly

You already call functions every day; this guide names what you have been doing. Following MDN's Functions, Arrow function expressions, and Rest parameters: declarations versus expressions, parameters and arguments, default values, rest parameters, spread syntax, return values, arrow function shorthand, the this trap, callbacks, and scope.

Tool TipsFrontend EngineeringAI Coding