<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kristof Kowalski on Medium]]></title>
        <description><![CDATA[Stories by Kristof Kowalski on Medium]]></description>
        <link>https://medium.com/@krzko?source=rss-cb7df1012d4f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nfPkN70QLXujaZAAZlNeqQ.png</url>
            <title>Stories by Kristof Kowalski on Medium</title>
            <link>https://medium.com/@krzko?source=rss-cb7df1012d4f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:59:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@krzko/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Regulars are the infrastructure]]></title>
            <link>https://medium.com/@krzko/regulars-are-the-infrastructure-7be6feaaabcc?source=rss-cb7df1012d4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/7be6feaaabcc</guid>
            <category><![CDATA[social-commerce-platform]]></category>
            <category><![CDATA[hyperlocal]]></category>
            <category><![CDATA[e-commerce-solution]]></category>
            <category><![CDATA[geolocation]]></category>
            <category><![CDATA[social-network]]></category>
            <dc:creator><![CDATA[Kristof Kowalski]]></dc:creator>
            <pubDate>Thu, 19 Mar 2026 03:25:50 GMT</pubDate>
            <atom:updated>2026-03-19T03:25:50.532Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T_Je3ODkrsvUGE1j1jLQVw.png" /></figure><h3>Every neighbourhood already has a network. Most products just ignore it.</h3><p>Walk into any good local café on a weekday morning and watch what happens.</p><p>The barista starts making a flat white before the order is placed. A nod replaces a greeting. Someone holds the door for a person they have never formally met, but have seen every Tuesday for two years.</p><p>That is not randomness. That is a social graph.</p><p>It is not stored in a database. It is not built by an algorithm. It is made of familiarity, repetition, and proximity. It exists in almost every neighbourhood on earth, and it is more durable than most things the internet has produced.</p><p>We call these people <strong>regulars</strong>.</p><p>They are the reason a suburb feels like somewhere, not just a set of coordinates. And they are the most undervalued layer in local technology.</p><p>This is something we think about constantly while building <a href="https://hyper.lc/">Hyper</a>: the neighbourhood already has infrastructure. Our job is to reveal it, not replace it.</p><h3>What makes a regular</h3><p>Regulars are not power users. They are not influencers. They are not necessarily even social.</p><p>A regular is someone who has a <strong>repeated relationship with a place</strong>.</p><p>That relationship can look like many things:</p><ul><li>the same coffee order, three mornings a week</li><li>the same corner of the same pub, every Friday</li><li>the same farmers market loop, every Saturday</li><li>the same park bench after school pickup</li></ul><p>What defines a regular is not frequency alone. It is <strong>commitment expressed through behaviour</strong>. They chose this place. They keep choosing it. And that choice carries more signal than any review or rating ever could.</p><p>When five strangers all independently become regulars at the same café, that tells you something about the café that no star rating can communicate. It tells you the place is worth returning to. Not once. Repeatedly.</p><p>That is a fundamentally different kind of trust signal.</p><h3>The invisible network that already works</h3><p>Every neighbourhood has a set of overlapping regular patterns. They form what you might call an informal local network, and it has real structure:</p><p><strong>Anchor places</strong> attract clusters of regulars. These are the venues that define the rhythm of a suburb. The pub that fills up on Wednesdays, not just Saturdays. The bakery with the weekend queue. The park where the same group of dog walkers congregate at 7am.</p><p><strong>Familiar strangers</strong> populate the gaps between close friends and total unknowns. You do not know their name. You have never spoken. But you recognise them, and that recognition creates a low-level sense of belonging.</p><p><strong>Informal connectors</strong> are the people who seem to know everyone. The bartender who introduces two regulars. The parent at school pickup who always knows what is on this weekend. The person who tried the new place first and told their group chat.</p><p><strong>Recurring rhythms</strong> bind it all together. Tuesday trivia. Thursday parmi night. Saturday market. Sunday family brunch. These are not events in the calendar sense. They are rituals that give a neighbourhood its texture.</p><p>This network functions without any app. It has for decades. But it has two significant limitations: it is invisible to anyone who is not already embedded in it, and it does not scale beyond word of mouth.</p><h3>Why this matters for local products</h3><p>If you are building a local product, you face a fundamental choice.</p><p><strong>Option A</strong>: manufacture a network from scratch. Import contacts, suggest connections, push notifications, gamify engagement. Build the graph synthetically and hope people participate.</p><p><strong>Option B</strong>: observe the network that already exists and make it legible.</p><p>Most products choose Option A because it is familiar. It is the global social playbook: acquire users, create content, drive engagement, monetise attention.</p><p>But local is different. The network is already there. The regulars already exist. The rhythms are already running.</p><p>The opportunity is not to build a new graph. It is to surface the one that is already operating, carefully, with permission, in a way that makes neighbourhood life easier for everyone involved.</p><p>That is the approach we are taking with Hyper.</p><h3>Regulars are the density you do not have to manufacture</h3><p>In a previous article, I wrote about why <a href="https://medium.com/@krzko/local-cold-start-is-the-real-boss-fight-6a3b961a7672">local cold start is the real boss fight</a>. The core problem is density: a local product needs enough activity in a small area to feel alive, and that is brutally hard to achieve from zero.</p><p>Regulars change the equation.</p><p>If you can identify and support the people who already have repeated relationships with local places, you do not need to manufacture density. You need to reveal it.</p><p>A suburb does not need 10,000 users to feel alive. It needs 50 regulars whose existing behaviour is reflected in the product. When those 50 people check in, share what is on, and surface real activity at real places, the neighbourhood starts to feel populated in a way that is honest rather than inflated.</p><p>This also solves a trust problem. When a new user opens a local app and sees activity from real locals at familiar places, the product feels credible. When they see generic content from strangers with no local context, it feels hollow.</p><p>Regulars provide the earliest and most authentic form of social proof a local product can have.</p><h3>What regulars need from a product (and what they do not)</h3><p>Here is the thing about regulars: they are not looking for a new platform to manage. They are busy. They are already out in the world. They do not want another feed to scroll or another profile to curate.</p><p>What regulars actually respond to:</p><p><strong>Low friction participation.</strong> A check-in that takes three seconds, not thirty. An optional note, not a mandatory post. The ability to contribute signal without performing for an audience.</p><p><strong>A personal record that feels valuable.</strong> Regulars care about their own patterns. Where they have been. What they liked. A personal map of neighbourhood life that builds over time without effort.</p><p><strong>Relevant local signal.</strong> Not a global feed. Not trending content from across the city. Just a clear view of what is happening nearby, filtered by the places and people they already care about.</p><p><strong>Privacy by default.</strong> Regulars will share their activity, but only if they trust the product. That means conservative defaults, clear visibility controls, and time-bounded presence. No one wants to broadcast their location to strangers indefinitely.</p><p><strong>Recognition without gamification.</strong> Regulars do not need badges or leaderboards. They need the product to understand that showing up regularly at the same places is meaningful, and to reflect that understanding in the experience. Not with trophies, but with relevance.</p><p>What regulars do not need: viral mechanics, influencer tools, content creation pressure, algorithmic feeds optimised for engagement, or any feature that treats them as an audience rather than a participant.</p><h3>Venues already know who their regulars are</h3><p>Ask any café owner, bartender, or restaurant manager and they will tell you the same thing: they know their regulars. They know when they come in. They know what they order. They know their name, or at least what they look like.</p><p>But that knowledge lives entirely in the heads of individual staff members. It is not captured anywhere. It is not transferable. When a barista leaves, a piece of the venue’s relationship layer walks out the door.</p><p>This is a real operational problem for local businesses.</p><p>A venue’s regulars are its most valuable customers. They drive reliable revenue. They bring friends. They leave reviews. They forgive bad days. They show up when it is quiet.</p><p>Yet most venues have no structured way to:</p><ul><li>understand who their regulars are beyond gut feel</li><li>communicate with them directly</li><li>reward them for loyalty</li><li>surface relevant information to them at the right time</li></ul><p>Loyalty cards and points programs try to solve this, but they are transactional. They reduce a rich, human relationship to a punch card.</p><p>What venues need is something closer to what the best bartender already does: recognise regulars, understand their patterns, and make their experience a little better because of the relationship. Except scaled beyond one person’s memory.</p><h3>Regulars as the bridge between social and commerce</h3><p>One of the patterns we keep returning to at Hyper is the relationship between social behaviour and commercial behaviour in local life.</p><p>In global platforms, social and commerce are usually separate products, or they are stitched together through advertising. You see an ad in your social feed. You click through to buy. The connection is artificial.</p><p>In local life, social and commerce are the same thing.</p><p>When you become a regular somewhere, you are doing both simultaneously. You are participating in the social life of the place, and you are transacting with a business. You are building a relationship, and you are spending money. Those are not two separate activities. They are one activity.</p><p>This is why regulars matter so much to the commerce layer we are building. They are the natural bridge between discovering a place, engaging with it socially, and transacting with it commercially.</p><p>When a regular checks in at their local pub, they are not just logging a visit. They are signalling ongoing intent. That signal is vastly more valuable than a one-time click on an ad, because it represents an actual, repeated, real-world relationship.</p><p>If you can serve regulars well, the commerce follows naturally. Not through interruption, but through relevance.</p><h3>What revealing the regular network looks like in practice</h3><p>This is not about surveillance. It is not about tracking people without consent. It is about designing a product that respects the patterns people are already living, and makes them visible in a way that benefits everyone.</p><p><strong>For the regular</strong>: you check in at your usual places. Over time, you build a personal map of your neighbourhood life. You see what is happening at places you care about. You discover things through locals, not algorithms. You get recognised for loyalty in a way that feels human, not gamified.</p><p><strong>For the venue</strong>: you see which locals return regularly. You understand patterns without guessing. You can surface an offer to your Tuesday crowd, or let your regulars know about a new menu item before anyone else. You build a direct, trust-based channel with the people who matter most to your business.</p><p><strong>For the neighbourhood</strong>: the live layer gets richer. New residents can see where locals actually go, not just what has the highest Google rating. The suburb develops a visible rhythm. Places that are genuinely loved become easier to find. The neighbourhood starts to feel more connected, even for people who are not deeply embedded yet.</p><h3>Regulars compound. That is the point.</h3><p>Global products chase novelty. They need new content, new users, new engagement every day. The machine runs on freshness.</p><p>Local products can work differently. They can run on repetition.</p><p>A regular who checks in three times a week generates more long-term value than a tourist who checks in once. Not because the individual data point is richer, but because the pattern compounds. Over weeks and months, the regular’s behaviour builds a picture of the neighbourhood that no single visit could provide.</p><p>When enough regulars contribute their patterns, the neighbourhood layer becomes self-sustaining. It does not need constant content creation. It does not need viral moments. It needs people doing what they already do, with a product that respects and reflects that behaviour.</p><p>That is why we believe regulars are the infrastructure.</p><p>Not the users. Not the audience. Not the creators.</p><p>The infrastructure.</p><p>They are the foundation on which everything else in a healthy local product is built: trust, density, commerce, discovery, and community.</p><h3>Where this is heading</h3><p>We are not building Hyper for influencers, power users, or content creators. We are building it for regulars.</p><p>For the person who has three places they go to every week and wants those places to know they exist. For the venue owner who wants to understand and reward the people who keep coming back. For the neighbourhood that already has a social graph but has no way to see it.</p><p>The infrastructure is already there. It just needs a surface.</p><p>If you are a regular somewhere, and you have ever wished that place knew how much you value it, that is exactly the feeling we are designing for.</p><p>What would your neighbourhood look like if the regular network was visible?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7be6feaaabcc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Whats On is the missing layer of local life]]></title>
            <link>https://medium.com/@krzko/whats-on-is-the-missing-layer-of-local-life-335c63bfab18?source=rss-cb7df1012d4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/335c63bfab18</guid>
            <category><![CDATA[whats-on]]></category>
            <category><![CDATA[social-network]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[geolocation]]></category>
            <category><![CDATA[hyperlocal]]></category>
            <dc:creator><![CDATA[Kristof Kowalski]]></dc:creator>
            <pubDate>Sun, 15 Feb 2026 00:40:10 GMT</pubDate>
            <atom:updated>2026-02-15T00:40:10.391Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EwSUAcsRCpV9aerpEm_-pA.png" /></figure><h3>Most of us run the same loop every week.</h3><p>You finish work and want something easy nearby.<br>You want to know if the local pub has trivia tonight.<br>You want to find a last minute table, a special, a happy hour, a gig, a market, a kids activity, or a place that simply feels lively.</p><p>And even though we live in a world of infinite apps, the answer is still fragmented.</p><ul><li>Google Maps is great for discovery, but it is not a live neighbourhood layer</li><li>Instagram is great for marketing, but it is not structured and it is easy to miss</li><li>Facebook events can work, but it feels noisy and impersonal</li><li>Group chats are reliable, but they do not scale beyond your circle</li><li>Posters and chalkboards are charming, but you only see them after you arrive</li></ul><p>So we end up doing what everyone does: we bounce between five different sources, make a guess, then hope it works out.</p><p>That gap is exactly why we are building <strong>Whats On</strong> in <a href="https://hyper.lc/">Hyper</a>.</p><p>Not another feed.<br>Not another directory.<br>A hyperlocal surface that rolls up what is happening nearby, based on real places and real updates, within a radius that matches real life.</p><h3>The core idea: local decisions are time, distance, and intent</h3><p>Most global products optimise for discovery at scale. They are built for browsing.</p><p>Local products should optimise for decision making in the moment.</p><p>Local decisions usually have three constraints:</p><h3>1. Time</h3><p>Is it happening now<br>Is it happening tonight<br>Is it recurring every Tuesday<br>Is it a lunch special that ends in 45 minutes</p><h3>2. Distance</h3><p>Is it walkable<br>Is it within a quick drive<br>Is it close enough to be spontaneous</p><h3>3. Intent</h3><p>What am I actually looking for<br>Food<br>Drinks<br>Something to do<br>A service<br>A job<br>A deal<br>A reason to leave the house</p><p>When those three dimensions align, local feels easy. When they do not, local feels like effort.</p><p><strong>Whats On is designed to compress that effort into one glance.</strong></p><h3>Why hyperlocal wins over global here</h3><p>A global feed can show you something interesting.<br>A hyperlocal surface can show you something actionable.</p><p>The difference is subtle but important:</p><ul><li>Global is entertainment</li><li>Hyperlocal is utility</li></ul><p>It is also why local is so hard. You cannot cheat with global content. If your neighbourhood is quiet, you have to design for quiet. If it is busy, you have to surface signal without turning the experience into chaos.</p><p>When Whats On works, it does one thing extremely well:</p><p><strong>It helps you decide what to do next, nearby, without overthinking.</strong></p><h3>Whats On is not just events. It is a rollup of the neighbourhood</h3><p>When people hear Whats On, they think of events calendars.</p><p>But neighbourhood life is richer than events.</p><p>A real local layer includes:</p><ul><li><strong>Offers</strong> from places, time-based and situational</li><li><strong>Events</strong> like trivia night, live music, tastings, markets, community sessions, sport</li><li><strong>Menus</strong> that tell you what a place actually serves, not just what category it sits in</li><li><strong>Services</strong> from local operators, salons, tradies, clinics, coaches</li><li><strong>Jobs</strong> posted by venues and local businesses hiring nearby</li></ul><p>Most platforms keep these as separate products, separate pages, separate searches.</p><p>Hyperlocal works best when these signals are composed into one surface.</p><p>That is what Whats On is for: a neighbourhood rollup that reflects what is available nearby, in a timeframe that matters.</p><h3>The power move: recurring programming makes local feel alive</h3><p>A big part of what makes a neighbourhood feel like it has texture is repetition.</p><ul><li>Tuesday trivia</li><li>Thursday parmi night</li><li>Friday happy hour</li><li>Saturday morning market</li><li>Sunday family sessions</li><li>Monthly community events</li><li>Seasonal specials</li></ul><p>This is where local differs from global again. Global thrives on novelty. Local thrives on rhythm.</p><p>Recurring programming also fixes a major local cold start issue: consistency. Even if the neighbourhood is not posting constantly, recurring events and offers provide a dependable backbone.</p><p>That is why we support recurring patterns for both offers and events. It makes Whats On useful even when volume is low, because rhythm fills the gaps.</p><h3>Offers are not ads. They are structured intent.</h3><p>Most people have a negative reaction to the word offers because they picture spam.</p><p>That is not what we are building.</p><p>In a hyperlocal context, offers are simply a structured way for a place to answer:</p><ul><li>What is worth knowing today</li><li>What is time-sensitive</li><li>What should a local consider right now</li></ul><p>A good offer is not a billboard. It is a nudge that aligns with real intent.</p><ul><li>It can be time-based, like happy hour</li><li>It can be limited, like first 50 claims</li><li>It can be linked to real behaviour, like rewarding first time visitors or repeat visits</li><li>It can be tied to moments, like checking in as you arrive</li></ul><p>The key is that the offer is not floating on the internet. It is bound to a real place, and it is discoverable when you are close enough for it to matter.</p><p>That is what gives hyperlocal offers their power. They are contextual, not broadcast.</p><h3>Whats On within a radius is the difference between browsing and doing</h3><p>A neighbourhood surface only works if it respects radius.</p><p>No one wants to see a great deal across town when they have 35 minutes free. No one wants to see a trivia night that is a 45 minute drive away when they are already out with friends.</p><p>Whats On is designed around a simple question:</p><p><strong>What is available near me, in the time window I care about?</strong></p><p>This sounds obvious, but it changes everything:</p><ul><li>it keeps the surface tight</li><li>it makes decisions faster</li><li>it reduces noise</li><li>it makes the product feel like it understands the user</li></ul><p>It is also how you get a local product to fit into real life. The session should be short. The result should be actionable.</p><h3>Whats On is a compounding surface for places</h3><p>For local venues and businesses, the challenge is always the same:</p><p>They have updates worth sharing, but they do not have time to be content creators.</p><p>Whats On helps because it gives businesses a structured way to participate without needing constant posting:</p><ul><li>Create an event once, set it to recur</li><li>Add an offer with a validity window</li><li>Update a menu without redesigning a website</li><li>List services so locals can discover them</li><li>Post a job and have it surface locally</li></ul><p>This is important: it reduces operational friction. The best local tools are not the ones with the most features. They are the ones that fit into a real shift, a real day, a real owner workflow.</p><p>When businesses can participate easily, the neighbourhood gets richer. When the neighbourhood gets richer, more locals return. When locals return, businesses see value. That is the loop.</p><h3>Whats On is also a trust engine</h3><p>Local discovery often fails because you do not trust what you are seeing.</p><ul><li>outdated listings</li><li>dead links</li><li>events that ended months ago</li><li>menu items that do not exist</li><li>offers that are not honoured</li><li>random blog posts from 2019</li></ul><p>A neighbourhood layer needs freshness and accountability. Binding information to real places, with time windows and visible status, is how you keep trust high.</p><p>That is why Whats On is built around structured objects: offers, events, menus, services, jobs. They can be time-bounded. They can expire. They can recur. They can be updated. They can be displayed consistently.</p><p>Trust is not a marketing line. It is a product outcome.</p><h3>What this feels like in practice</h3><p>Here are a few simple, real scenarios that show why hyperlocal wins.</p><h3>Scenario 1: Friday night, no plan</h3><p>You open Whats On within a small radius. You see:</p><ul><li>trivia at a pub nearby</li><li>a live music event starting soon</li><li>a couple of places with food specials</li><li>a venue with a limited offer running for two hours</li></ul><p>You make a decision in 20 seconds, not 20 minutes.</p><h3>Scenario 2: Saturday morning local routine</h3><p>You see:</p><ul><li>the market that is on every weekend</li><li>a cafe with a new menu item</li><li>a local service that has availability today</li><li>an event for families nearby</li></ul><p>It becomes a neighbourhood dashboard, not a social feed.</p><h3>Scenario 3: You move to a new suburb</h3><p>Instead of trawling reviews, you can see:</p><ul><li>what locals actually do</li><li>where events happen regularly</li><li>which places are actively publishing menus and updates</li><li>which venues are hiring</li><li>which services are available nearby</li></ul><p>You get a sense of the rhythm of the suburb faster.</p><h3>Why we are building this now</h3><p>We have already built the foundations that make Whats On possible:</p><ul><li>offers</li><li>events</li><li>menus</li><li>jobs</li><li>services</li></ul><p>Whats On is where all of that becomes a single user value proposition.</p><p>Without Whats On, these features are useful but fragmented.</p><p>With Whats On, the product becomes a neighbourhood utility:</p><p><strong>open app, see what is on nearby, decide quickly, go.</strong></p><p>It is also the cleanest bridge between social and commerce without forcing anything.</p><p>Social tells you what is happening.<br>Commerce makes it easier to act on it.</p><p>But the order matters. Utility first. Density first. Trust first.</p><h3>The bigger vision: a calmer local internet</h3><p>A lot of modern software feels like it is competing for attention.</p><p>Hyperlocal can be different.</p><p>The best local product is one you use for 10 seconds, then put your phone away because you now know what to do.</p><p>That is the design goal for Whats On:</p><ul><li>short sessions</li><li>high signal</li><li>real places</li><li>real timing</li><li>minimal noise</li></ul><p>When local works, it strengthens community. It helps venues thrive. It makes neighbourhood life easier. It makes the internet feel human again.</p><h3>If you are building local, I would love your take</h3><p>Whats On is our attempt to bring those together into one simple surface that actually helps people decide what to do nearby.</p><p>If you could wave a wand and improve one thing about how you discover what is on in your suburb, what would it be?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=335c63bfab18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Local cold start is the real boss fight]]></title>
            <link>https://medium.com/@krzko/local-cold-start-is-the-real-boss-fight-6a3b961a7672?source=rss-cb7df1012d4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a3b961a7672</guid>
            <category><![CDATA[commerce]]></category>
            <category><![CDATA[social-network]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[hyperlocal]]></category>
            <category><![CDATA[geolocation]]></category>
            <dc:creator><![CDATA[Kristof Kowalski]]></dc:creator>
            <pubDate>Mon, 02 Feb 2026 12:28:48 GMT</pubDate>
            <atom:updated>2026-02-02T12:28:48.880Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jnzlgnykODZzq6npyLpu-Q.png" /></figure><p>If you have ever built anything local-first, you know the uncomfortable truth: the hardest part is not the map, the mobile app, the backend, or even the business model.</p><p>The hardest part is <strong>density</strong>.</p><p>Local products do not fail because the idea is bad. They fail because the first experience is empty, and emptiness kills belief. A user opens the app, sees nothing happening, and leaves. A venue looks at a dashboard with no activity and loses interest. A community page with no community is just a page.</p><p>That is why I think local cold start is the real boss fight. Not acquisition. Not virality. Density.</p><p>This is our current obsession as we build Hyper: how to make a neighbourhood product feel alive early, without faking it, without burning trust, and without requiring a global-scale marketing machine.</p><p>This is our take on the problem and the playbook we are using to work through it.</p><h3>The cold start problem in local is not one problem. It is three.</h3><p>Most people talk about cold start like it is a single hurdle. In local, it is a stacked set of constraints that compound:</p><h3>1. Geographic fragmentation</h3><p>A global social product can onboard one user and immediately show them content from millions of people worldwide.</p><p>A local product cannot. The user in Yarraville does not care what is happening in New York, and they should not have to. If you show them global content, you have broken the promise in the first session.</p><p>Local means your network is fragmented into thousands of tiny networks. You are solving the same problem over and over again, suburb by suburb.</p><h3>2. Temporal volatility</h3><p>Local is not just about where. It is also about <strong>when</strong>.</p><p>A neighbourhood can feel alive at 8am, quiet at 2pm, active again at 6pm, then silent overnight. That means the product must work across time windows, not just across users.</p><p>If you do not design for time, the app feels dead even when the neighbourhood is not.</p><h3>3. Social trust and privacy</h3><p>Local is intimate. It is closer to real life. That makes it valuable, but also sensitive.</p><p>People will not share location or activity if they feel exposed. If you make privacy clunky, you lose participation. If you make privacy unclear, you lose trust.</p><p>The trade-off is brutal: you need enough signal to feel alive, but you need to earn it carefully.</p><h3>Why local emptiness feels worse than global emptiness</h3><p>A blank social feed is bad. A blank neighbourhood product is worse.</p><p>When a global product is empty, the user assumes they arrived early or need to follow more people. They often blame themselves.</p><p>When a local product is empty, the user assumes the product is not real, or nobody uses it, or it will never work in their area. They blame the product.</p><p>That is because local products are implicitly making a promise:</p><blockquote><em>This will show you what is happening around you.</em></blockquote><p>If it cannot do that immediately, the value proposition collapses.</p><h3>The core insight: you are not building an app, you are bootstrapping a local graph</h3><p>Local is fundamentally a graph problem: <strong>people + places + activity</strong>.</p><p>You are not just shipping features. You are creating:</p><ul><li>recurring interactions</li><li>repeatable rituals</li><li>trusted participation</li><li>density in a defined geography</li></ul><p>This changes how you think about v1.</p><p>Your initial goal is not to look feature complete. Your initial goal is to create <strong>enough repeated behaviour</strong> that the neighbourhood starts to feel alive.</p><p>That is the minimum viable neighbourhood.</p><h3>The first 100 users are not one cohort. They are four stages.</h3><p>We think about early density in stages. Each stage has a different goal and different failure modes.</p><h3>Stage 1: The first 10</h3><p>Goal: prove the loop works for someone you can talk to.</p><p>What matters:</p><ul><li>the product opens fast</li><li>the core action is obvious</li><li>it feels safe to participate</li><li>the first interaction creates value immediately</li></ul><p>At this stage, you are not measuring retention statistically. You are watching behaviour and asking one question:</p><p><strong>Did this feel like work, or did it feel like a moment?</strong></p><h3>Stage 2: The first 25</h3><p>Goal: create the first hints of social proof.</p><p>What matters:</p><ul><li>users can discover a few places easily</li><li>users see at least some recent activity</li><li>the app starts to feel like it is about the neighbourhood, not about the founder</li></ul><p>This is where you start seeing whether people will contribute without being asked.</p><h3>Stage 3: The first 100</h3><p>Goal: establish recurring use cases.</p><p>What matters:</p><ul><li>people return because it helps them decide or remember</li><li>the content is local enough to feel relevant</li><li>the neighbourhood starts to develop patterns</li></ul><p>This is where the product becomes real. If you cannot get here, nothing else matters.</p><h3>Stage 4: The first 300 to 500</h3><p>Goal: unlock the second layer of value.</p><p>What matters:</p><ul><li>meaningful clusters form around places</li><li>there is enough activity to power discovery</li><li>you can start introducing secondary features without the app feeling empty</li></ul><p>Only after this do you earn the right to scale to the next neighbourhood.</p><h3>The three things you need to seed in local</h3><p>Most teams try to seed users and hope content appears.</p><p>That is not enough.</p><p>Local needs three seeds, and they must be sequenced properly:</p><h3>1. Seed places</h3><p>The neighbourhood must feel navigable on day one.</p><p>Even with zero users, the user should be able to explore places and feel like the app knows the area. If your place layer is weak, everything feels fake.</p><p>Seeding places is not the same as building a directory. It is about:</p><ul><li>correct and familiar place names</li><li>clean categories</li><li>reliable search</li><li>stable place pages</li></ul><p>This is table stakes. Without it, the product feels unfinished.</p><h3>2. Seed activity</h3><p>People do not show up to an empty room.</p><p>You need the product to show some signs of life early. The mistake many products make is faking it in a way that breaks trust.</p><p>There is a difference between:</p><ul><li>highlighting real activity from a small alpha group, and</li><li>manufacturing activity that did not happen</li></ul><p>We are biased towards honest activity, even if it is low volume, because local trust is fragile. If you burn it, you cannot buy it back.</p><h3>3. Seed social edges</h3><p>Users need at least a few meaningful connections, quickly.</p><p>A local product without any social edges becomes a utility app. That can still work, but it changes the product entirely.</p><p>You need to help people:</p><ul><li>find locals they already know</li><li>follow a few relevant accounts</li><li>see familiar activity in the feed</li></ul><p>Not by spamming them with suggested users. By making it effortless to connect to real people in the neighbourhood.</p><h3>The local cold start loop: Reduce friction, increase reward, earn trust</h3><p>If you want density, you need contribution. If you want contribution, you need to make the answer to this question obvious:</p><p><strong>Why should I do this right now?</strong></p><p>Our approach is to treat every early action as a trade:</p><ul><li>The user gives attention, and sometimes location.</li><li>The product must give back something useful immediately.</li></ul><p>That means three levers:</p><h3>1. Reduce friction</h3><p>The action must be fast.<br>If checking in feels like filling out a form, you lose.</p><p>The product should feel like:</p><ul><li>a tap</li><li>a choice</li><li>optional context</li><li>done</li></ul><p>You are competing with real life. People are out. They are with friends. They do not want to type.</p><h3>2. Increase immediate reward</h3><p>The check-in has to do something.</p><p>Not in a gamified, vanity way. In a utility way.</p><p>Examples of immediate reward patterns:</p><ul><li>the user sees their activity appear in a clean timeline</li><li>the place page updates with fresh signal</li><li>the user builds a personal history that feels valuable</li><li>the user sees lightweight social proof that a place is active</li></ul><p>The principle is simple: participation creates a visible effect.</p><h3>3. Earn trust progressively</h3><p>Local products die when they demand too much too early.</p><p>You should not ask a new user to share precise location, show presence, and post publicly in the first 30 seconds.</p><p>You should earn it:</p><ul><li>start with while-using permissions</li><li>default to conservative visibility</li><li>make it clear what others can see</li><li>make it easy to opt out</li></ul><p>Trust is not a setting. It is a sequence.</p><h3>What success looks like in an early neighbourhood</h3><p>We do not think about success as total downloads. We think about signals that density is forming.</p><p>Here are examples of neighbourhood health metrics we care about early:</p><ul><li><strong>Repeat behaviour</strong>: people checking in multiple times per week</li><li><strong>Place clustering</strong>: a small set of places repeatedly showing activity</li><li><strong>Social edges</strong>: users following locals and seeing relevant activity</li><li><strong>Low friction</strong>: check-ins completed quickly, without abandonment</li><li><strong>Trust adoption</strong>: gradual opt-ins to richer features, without backlash</li></ul><p>These are not vanity metrics. They are indicators that the product is becoming part of neighbourhood life.</p><h3>Why we are starting suburb by suburb</h3><p>Scaling a local product is not copying and pasting a growth plan.</p><p>Each suburb is its own ecosystem:</p><ul><li>its own rhythms</li><li>its own social fabric</li><li>its own venue mix</li><li>its own definitions of what is good</li></ul><p>Starting suburb by suburb is not a limitation. It is the strategy.</p><p>If you can win one neighbourhood, you learn:</p><ul><li>what actually drives repeat behaviour</li><li>which places become anchors</li><li>how users invite others</li><li>what kinds of content and activity feel natural</li></ul><p>Then you can move outward with confidence.</p><h3>The honest truth: local is slower, but it compounds differently</h3><p>Global products can grow fast because their content pool is limitless. Local is slower because density must be earned.</p><p>But when it works, it compounds in a different way:</p><ul><li>neighbourhoods have memory</li><li>routines repeat</li><li>regulars return</li><li>communities reinforce themselves</li></ul><p>You are not chasing infinite novelty. You are serving a living system.</p><p>That is why local matters, and why it is so hard.</p><h3>Where Hyper fits in this</h3><p><a href="https://hyper.lc/">Hyper</a> is built around the belief that the neighbourhood deserves its own live layer.</p><p>We are starting with the fundamentals:</p><ul><li>people</li><li>places</li><li>activity check-ins</li></ul><p>We are focusing on making the experience feel alive and useful in a small pilot area before expanding.</p><p>Because until a neighbourhood has density, nothing else matters.</p><p>Local cold start is the boss fight. We are building for that fight.</p><p>If you have built local products before, I would genuinely love your perspective.</p><p>What did you do to solve density, and what did you do that you would never do again?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a3b961a7672" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why local matters (even in a world that optimises for global)]]></title>
            <link>https://medium.com/@krzko/why-local-matters-even-in-a-world-that-optimises-for-global-97d9b2562f61?source=rss-cb7df1012d4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/97d9b2562f61</guid>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[hyperlocal]]></category>
            <category><![CDATA[social-network]]></category>
            <category><![CDATA[geolocation]]></category>
            <dc:creator><![CDATA[Kristof Kowalski]]></dc:creator>
            <pubDate>Tue, 13 Jan 2026 23:24:57 GMT</pubDate>
            <atom:updated>2026-01-13T23:24:57.667Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xiLAWTrZEMxQzTIufYzFJg.png" /></figure><p>The internet taught an entire generation to think globally by default.</p><p>You can follow anyone, anywhere. You can buy almost anything with two taps. You can watch the same trends, memes, and top 10 lists as everyone else. We’ve built extraordinary systems for distribution at scale.</p><p>But there’s a trade off we don’t talk about enough:</p><p>As products optimise for global reach, they often become less useful for the place you actually live.</p><p>And the place you live, your suburb, your neighbourhood, the cafés you frequent, the people you bump into, the venues that hold your memories. Still matters more than most people admit.</p><p>Local isn’t nostalgia. Local is infrastructure for a good life.</p><p>This is one of the core beliefs behind what we’re building with Hyper: a local first layer that treats neighbourhood life as the starting point, not a filtering option.</p><h3>Global scales content. Local scales life.</h3><p>Global platforms are incredible at one thing: <em>distribution</em>.</p><p>They excel at broadcasting information to billions of people, extracting attention, and compressing diverse experiences into a uniform feed. They are built to answer questions like:</p><ul><li>What is trending right now?</li><li>What is the best restaurant in the world/city?</li><li>What is everyone talking about today?</li></ul><p>Those are valid questions.</p><p>But local questions look different:</p><ul><li>Where can I grab a great coffee within 10 minutes?</li><li>Which pub is lively on a Wednesday, not just Saturday?</li><li>What’s on nearby <em>tonight</em>?</li><li>Where do people like me actually go after work?</li><li>Is anyone I know around?</li></ul><p>These aren’t global questions. They’re situational. They’re time-bound. They’re human.</p><p>The closer the question gets to your real life, the less useful global optimisation becomes.</p><h3>Local is layered. That’s the point.</h3><p>When people talk about local, they often imagine a single radius on a map.</p><p>In reality, local is multiple layers… and each layer has a different kind of value:</p><h3>1) The physical layer</h3><p>Your actual geography: streets, parks, cafés, pubs, shops, venues. This is the layer where time and distance matter. Ten minutes versus thirty changes decisions.</p><h3>2) The social layer</h3><p>Your familiar strangers, regulars, friends, parents from school, people you see at the same spots. Most neighbourhoods have a social network already, it just isn’t visible or organised.</p><h3>3) The cultural layer</h3><p>The vibe that makes places feel like <em>your</em> place: the gig nights, the community events, the local rituals, the Sunday routines. This is identity, not just coordinates.</p><h3>4) The economic layer</h3><p>The independent businesses, services, and operators who keep the neighbourhood alive. Local commerce isn’t an abstract concept, it’s jobs, livelihoods, and community stability.</p><h3>5) The trust layer</h3><p>Local carries trust differently. You don’t need a thousand reviews when you can see: people I know go here or locals are actually showing up.</p><p>Global apps flatten these layers. Local first products can embrace them.</p><h3>Local has an unfair advantage: an existing base of real people</h3><p>Here’s the part that’s easy to miss when building products: local has something global always struggles to manufacture.</p><p>A neighbourhood already has:</p><ul><li>regulars</li><li>routines</li><li>hangouts</li><li>informal leaders</li><li>tight feedback loops</li><li>real world consequences</li></ul><p>You don’t need to invent a community from scratch. You need to reveal it, support it, and make it easier for people to participate on their own terms.</p><p>That is fundamentally different from building a global audience where people follow you for content and leave when the algorithm changes.</p><p>Local communities are stickier because they are anchored in physical reality.</p><h3>Local can be social, but it doesn’t have to be</h3><p>One misconception is that local first means forced social or constant interaction.</p><p>In reality, local works precisely because it can serve different modes:</p><h3>“I want connection” mode</h3><ul><li>Meet friends</li><li>See where people are</li><li>Discover where your crowd hangs out</li><li>Feel part of something</li></ul><h3>“I want utility” mode</h3><ul><li>Find what’s nearby quickly</li><li>See what’s on today</li><li>Make a decision without overthinking</li><li>Get in and out without a chatty feed</li></ul><h3>“I want privacy” mode</h3><ul><li>Quietly track your own routines</li><li>Build a personal map of places you like</li><li>Keep your presence limited, opt-in, and time bound</li></ul><p>A good local product respects all three. It gives you agency. It doesn’t force you into performative posting just to get value.</p><p>That’s important, because local life is personal. It’s not always meant for broadcasting.</p><h3>Local is where context finally becomes real</h3><p>Tech has spent years chasing personalisation, but often it’s just:</p><ul><li>content recommendations based on clicks</li><li>ads based on inferred interests</li><li>broad segmentation</li></ul><p>Local context is richer and more grounded:</p><ul><li>Where are you?</li><li>What time is it?</li><li>What are you doing?</li><li>What’s your constraint?</li><li>What’s the weather?</li><li>Are you alone or with others?</li><li>Are you walking, commuting, already out?</li></ul><p>Those details change what useful means in a moment.</p><p>Global platforms usually ignore this because their goal is scale and engagement.</p><p>Local first products can use context to reduce friction and increase relevance, not to maximise time spent.</p><p>That’s the difference between a feed and a neighbourhood layer.</p><h3>Local commerce is more human than global commerce</h3><p>Global commerce is optimised for:</p><ul><li>convenience</li><li>price competition</li><li>infinite choice</li><li>standardised delivery</li></ul><p>Local commerce is something else:</p><ul><li>it’s relationship-based</li><li>it rewards regulars</li><li>it thrives on small moments</li><li>it’s driven by trust and familiarity</li><li>it has personality</li></ul><p>There’s a reason people still choose their local café even when they could make coffee at home. Or why they have their pub. Or why they’ll pay a bit more for a local butcher who knows them.</p><p>Those aren’t transactional relationships. They’re part of how neighbourhood identity forms.</p><p>A local first platform can support that without turning it into a soulless ad marketplace. It can help places be discovered, help locals feel seen, and eventually make it easier for businesses to transact with people who are already nearby and ready.</p><p>That’s also why we’re interested in layering in store like features over time, not as a generic marketplace, but as an extension of real-world interactions people are already having.</p><p>Importantly: it shouldn’t require everyone to become a content creator. Local businesses are busy. Locals are busy. Local works when it’s lightweight.</p><h3>Global-first often creates sameness. Local-first preserves difference.</h3><p>Global feeds are efficient. But they also homogenise.</p><ul><li>The same coffee aesthetic everywhere</li><li>The same viral food items</li><li>The same best of lists</li><li>The same influencer driven recommendations</li></ul><p>Local is the antidote to that. It keeps neighbourhoods distinct. It preserves the hidden gems and the weird little rituals that don’t make sense outside the context of that place.</p><p>In a world where everything is optimised for sameness, local becomes more valuable, not less.</p><h3>Start local, earn trust, then expand</h3><p>This is the part that matters if you’re building a product:</p><p>Local first doesn’t mean small forever. It means:</p><ul><li>start with a neighbourhood</li><li>make it genuinely useful there</li><li>build density and trust</li><li>learn the real patterns</li><li>then expand outward deliberately</li></ul><p>If it doesn’t work in one suburb, scaling it globally won’t fix it. It will just scale the emptiness.</p><p>Global expansion is great, but it should be earned through local success, not substituted for it.</p><h3>The future is not global or local. It’s both, but local first.</h3><p>I’m not anti global. Global reach is powerful, and the best products eventually travel.</p><p>But local is where life happens.</p><p>Local is where community is real. Local is where trust forms. Local is where businesses survive. Local is where your routines and memories live. Local is where what’s happening right now? actually matters.</p><p>That’s why we’re building local first.</p><p>Not because global isn’t valuable, but because local is undervalued, and because the next generation of neighbourhood products should serve people where they actually are, not just where the algorithm can send them.</p><p>If you’re building in local, maps, marketplaces, social, or anything that touches the real world: I’d love to hear your take.</p><p>What do you think global platforms still get wrong about local life?</p><p><a href="https://www.linkedin.com/preload/#">Kristof Kowalski</a> — Hyper Founder</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97d9b2562f61" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Check-in 2.0 — Why this tiny interaction still matters]]></title>
            <link>https://medium.com/@krzko/check-in-2-0-why-this-tiny-interaction-still-matters-0ab811b176ba?source=rss-cb7df1012d4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/0ab811b176ba</guid>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[social-network]]></category>
            <category><![CDATA[check-in]]></category>
            <category><![CDATA[geolocation]]></category>
            <category><![CDATA[hyperlocal]]></category>
            <dc:creator><![CDATA[Kristof Kowalski]]></dc:creator>
            <pubDate>Thu, 08 Jan 2026 08:53:13 GMT</pubDate>
            <atom:updated>2026-01-08T08:53:13.759Z</atom:updated>
            <content:encoded><![CDATA[<h3>Check-in 2.0 — Why this tiny interaction still matters</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IoPYoKEslUtATZtcycwHLQ.png" /></figure><h3>Check-in 2.0 — why this tiny interaction still matters</h3><p>Fifteen years ago, the simple act of a check-in felt magical.</p><p>Foursquare, Gowalla and others turned <strong>I am here</strong> into a social signal. You’d check in at a bar or café, collect a badge, maybe become <strong>mayor</strong>, and see where your friends had been. For a while it genuinely changed how a lot of us moved through cities.</p><p>And then check-ins faded into the background.</p><p>The products either pivoted into enterprise, narrowed into niche communities, or leaned into ad-heavy models that didn’t match the value of the behaviour. Check-ins became a novelty rather than a core primitive.</p><p>I don’t think the check-in failed. I think we stopped evolving it.</p><p>What we’re building with <strong>Hyper</strong> starts from a simple belief:</p><p>A check-in isn’t a vanity action. It’s one of the most honest expressions of local intent we have:</p><blockquote><em>I chose to spend my time, money and attention here, now, doing this.</em></blockquote><p>If we treat it with that level of respect, a check-in becomes more than a breadcrumb. It becomes the foundation for a richer <strong>local layer</strong> than most apps have ever managed to deliver.</p><h3>People dedicate time and effort — the check-in should reflect that</h3><p>When someone checks in, they’ve already done the hard part:</p><ul><li>They left the house.</li><li>They chose a place out of dozens of options.</li><li>They committed their time, money, attention and social energy.</li></ul><p>Yet in most apps, that decision is stored like a sterile log entry:</p><blockquote><em>User </em><strong><em>X</em></strong><em> visited Place </em><strong><em>Y</em></strong><em> at Time </em><strong><em>Z</em></strong><em>.</em></blockquote><p>That’s useful for a heatmap, a leaderboard, or a recap. But it strips out what actually mattered in the moment:</p><ul><li><strong>What were they doing?</strong> Coffee and laptop? Dinner with kids? A quick drink after work?</li><li><strong>Who were they with?</strong> Partner, friends, colleagues, alone?</li><li><strong>What was the constraint?</strong> 20 minutes between meetings, a long Sunday, a school-night curfew?</li><li><strong>What was the intent?</strong> Discover something new, stick to the usual, celebrate, decompress?</li></ul><p>We talk a lot about <strong>personalisation</strong> in tech, but this is the kind of context that rarely makes it into the model. And without it, local apps struggle to be genuinely useful beyond novelty.</p><p><strong>Check-in 2.0</strong>, as we see it, is:</p><blockquote><strong><em>Person + Place + Activity + Time + Context</em></strong><em><br>…not just </em><strong><em>I was here</em></strong><em>.</em></blockquote><p>Not more friction. Just more meaning.</p><h3>Check-in 1.0: what we loved, and what was missing</h3><p>The first generation of check-in products got a lot right:</p><ul><li>They made places feel alive.</li><li>They turned cities into playful layers of badges, mayorships and tips.</li><li>They built strong early communities.</li></ul><p>But structurally, they ran into three recurring issues.</p><h3>1) Not enough utility beyond the novelty</h3><p>Once the game wore off, the everyday value for most people wasn’t strong enough to build a habit. The check-in remained fun, but not essential.</p><h3>2) Weak connection to sustainable business models</h3><p>Many products ended up chasing ads or SMB subscriptions without a deep link between the check-in and a measurable outcome. It’s hard to build a durable business when the core behaviour isn’t directly tied to value exchange.</p><h3>3) Limited sense of right now</h3><p>A lot of the experience was historical: where people had been, what they rated, what they posted. Useful, but not the same as a live pulse of what’s happening around you in this moment.</p><p>At the same time, platforms like Google Maps and Instagram filled in gaps for search, reviews, photos and events. But they didn’t fill the gap that the early check-in era hinted at: a <strong>live, hyperlocal layer</strong> that’s both social and practical.</p><p>We’re not trying to recreate Foursquare. We’re trying to take the best parts of that era and anchor them in real utility, with a clear path to durability.</p><h3>The why behind Check-in 2.0</h3><p>From our perspective, a modern check-in should create value for <strong>three parties at once</strong>: the person, the place, and the neighbourhood.</p><h3>1) For people: better decisions, better memories, better presence</h3><p><strong>Decision support</strong><br>When you open an app while standing on a street corner, you don’t want infinite content. You want fast, relevant answers:</p><blockquote><em>Given who I am, what I’m doing, and how much time I’ve got, what’s a good option nearby?</em></blockquote><p>That’s the real job-to-be-done. Not scrolling. Not browsing. Deciding.</p><p><strong>Lightweight memory</strong><br>Most of us don’t want to keep a journal. But we do want a gentle record of our local life: where we went, what we did, what we loved. A check-in is a simple, low-lift way to capture that without making it a chore.</p><p><strong>Presence, not surveillance</strong><br>There’s also a genuine human value in knowing where your people are — but only if it’s handled carefully. Presence should be opt-in, scoped, and time-bound. Enough to create serendipity, without drifting into creepy tracking.</p><h3>2) For places: real signal, not more noise</h3><p>Most local businesses don’t need another platform yelling <strong>post more</strong>.</p><p>They need:</p><ul><li>A clearer picture of real behaviour: <strong>who comes, when, and for what kind of activity</strong>.</li><li>A lightweight way to communicate: <strong>this is what’s on today</strong> without needing a full-time social media manager.</li><li>A path from <strong>signal → outcome</strong> (footfall, orders, bookings), not just impressions and likes.</li></ul><p>When check-ins carry meaning, they can help places understand the difference between:</p><ul><li>the <strong>coffee + laptop</strong> crowd</li><li>quick lunches</li><li>family dinners</li><li>Friday-after-work drinks</li></ul><p>That’s operationally useful. It’s not just marketing.</p><h3>3) For the neighbourhood: a live layer on top of the map</h3><p>Neighbourhoods already have a social graph:</p><ul><li>baristas and bartenders who know the regulars</li><li>locals who always discover the new spot first</li><li>parents, runners, dog walkers, commuters, remote workers</li></ul><p>The problem is that graph is mostly invisible unless you’re already embedded in it.</p><p>Check-ins, done well, can make the neighbourhood a little more navigable:</p><ul><li>Where does this area actually spend its time?</li><li>Which places are true local favourites vs one-off destinations?</li><li>What’s the live pulse at lunchtime, after work, on weekends?</li></ul><p>That’s bigger than a feed. It’s a neighbourhood layer.</p><h3>How we’re approaching this with Hyper (without turning it into another feed)</h3><p>With Hyper, we treat the check-in as the atomic interaction. Everything else hangs off it:</p><ul><li><strong>People</strong> — who you are and who you follow</li><li><strong>Places</strong> — the venues around you</li><li><strong>Activity</strong> — what you’re doing there</li><li><strong>Context</strong> — just enough detail to make it useful</li></ul><p>Product-wise, that translates to a few non-negotiables:</p><ul><li>The act of checking in must be <strong>fast</strong>.</li><li>We ask for <strong>just enough context</strong> to increase usefulness (activity type, optional note/media).</li><li>Privacy and presence are <strong>clear, opt-in, and respectful by default</strong>.</li><li>The experience is designed around <strong>right now nearby</strong>, not an infinite scroll.</li></ul><p>And importantly: we’re <strong>starting small</strong>. Suburb by suburb. Neighbourhood by neighbourhood. If it doesn’t feel great in one local area, it has no business trying to be global.</p><h3>The vision: check-ins as a serious primitive again</h3><p>The long-term vision is not <strong>bring check-ins back</strong> for nostalgia’s sake.</p><p>It’s to make them useful again:</p><ul><li>A daily utility for people: log what you’re doing, decide where to go, keep a gentle memory of your local life.</li><li>A signal layer for places: understand and serve the real patterns of locals, not just generic foot traffic.</li><li>A foundation for richer local experiences over time, built on real-world behaviour rather than noise.</li></ul><p>In other words:</p><p><strong>Check-in 1.0</strong> was: <strong>I was here</strong>.<br><strong>Check-in 2.0</strong> is: <strong>I chose to be here, doing this — and that choice can safely power something useful</strong>.</p><p>We’re not claiming this is solved. We’re building towards it.</p><p>If you’re working in local, social, marketplaces or maps — or if you remember the early check-in era and feel like there’s unfinished business — I’d love to compare notes.</p><p><a href="https://hyper.lc/">Hyper</a> is in private preview right now, and we’re hyped to show you what we’ve been cooking behind the scenes.</p><p>— Kristof Kowaski | Hyper Founder</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0ab811b176ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>