<?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 Mirislom M. on Medium]]></title>
        <description><![CDATA[Stories by Mirislom M. on Medium]]></description>
        <link>https://medium.com/@mirislamyoldash?source=rss-e33c96ae2dd1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Mirislom M. on Medium</title>
            <link>https://medium.com/@mirislamyoldash?source=rss-e33c96ae2dd1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:52:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mirislamyoldash/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[BlindLine — Connecting Blind Travelers With Helping Hands]]></title>
            <link>https://medium.com/@mirislamyoldash/blindline-connecting-blind-travelers-with-helping-hands-70d621e3bef2?source=rss-e33c96ae2dd1------2</link>
            <guid isPermaLink="false">https://medium.com/p/70d621e3bef2</guid>
            <category><![CDATA[belgium]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[antwerp]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Mirislom M.]]></dc:creator>
            <pubDate>Wed, 25 Mar 2026 01:10:37 GMT</pubDate>
            <atom:updated>2026-03-25T01:10:37.967Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine deciding on a Tuesday morning that you want to take the train to Ghent, Belgium. You find the 10:42 departure and you’re on the platform nine minutes later. Easy. Now imagine you’re visually impaired. Belgium’s national rail operator (NMBS/SNCB) requires passengers with disabilities to register their journey <strong>at least 24 hours in advance</strong> to receive assistance. Your spontaneous Tuesday trip? Not happening.</p><p>We are a team of students who spent the past weeks building <strong>BlindLine</strong> — a React Native mobile app that connects visually impaired travelers (<strong>VIPs</strong>) with nearby volunteers in real time. No central operators. No waiting lists. Just two people, a matched trip, and a shared train.</p><h3>The Client: De Markgrave</h3><p>BlindLine was built for <a href="https://www.demarkgrave.be/"><strong>De Markgrave</strong></a>, an Antwerp-based care and knowledge organisation that has been supporting blind and visually impaired people for decades. Their tagline — <em>“Samen zien we meer”</em> (“Together we see more”) — captures what they do well: they offer everything from visual rehabilitation and assisted living to activity centres and specialised education, all centred around one goal: letting people with a visual impairment live life to the fullest.</p><figure><img alt="DeMarkgrave Banner" src="https://cdn-images-1.medium.com/max/1024/1*RiDjMbcZD1d4HUjrLx8VQA.png" /></figure><p>De Markgrave came to us with the idea for BlindLine. We sat down with them to nail down the scope, aligned on what was feasible, and got to work. A few weeks into development we demoed what we had — they gave feedback, we implemented it, and iterated through to a finished product. Having a client who both deeply understands their users and is genuinely invested in the outcome made a real difference. They didn’t just hand us a brief; they brought lived experience with the exact problem we were trying to solve.</p><h3>Designing for Someone Who Can’t See Your UI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*mD46oMgslNtK5oFjwQT6Fg.png" /></figure><p>Here’s the central irony of this project: your primary user <em>cannot see the interface</em>. That constraint doesn’t just influence the design — it dominates it.</p><p>Both iOS and Android ship with built-in screen readers — <strong>VoiceOver</strong> on iOS and <strong>TalkBack</strong> on Android. These tools read out whatever is on screen and let users navigate entirely by swipe gestures and double-taps, without ever needing to see a pixel. For BlindLine to work for its core audience, <strong>every single interactive element</strong> needed to be compatible with both.</p><p>In React Native, that means two things. First, every touchable element needs a clear accessibilityLabel — not just the icon or visual hint a sighted user would see, but a full spoken description. A button that visually shows a green checkmark needs a label like <em>&quot;Accept trip request&quot;</em>, not <em>&quot;Button&quot;</em>. Second, the navigation flow itself must be logical when read linearly. TalkBack and VoiceOver move through elements in DOM order, so a layout that looks fine on screen can sound completely incoherent to a screen reader if the component order doesn&#39;t match the reading order.</p><p>The entire VIP side of the app — from onboarding through to requesting a trip and reviewing your volunteer — is navigable from start to finish using only TalkBack swipes and double-taps. No sighted assistance required at any point.</p><p>One detail that took iteration: <strong>modal overlays </strong>(pop-up screens that appear on top of the current page, such as confirmation dialogs or pickers). When a modal opens, TalkBack should trap focus inside it so the user doesn’t accidentally swipe back to the content underneath. React Native’s accessibilityViewIsModal prop handles this, but it&#39;s easy to forget until you actually test with a screen reader switched on — something we started doing after our first round of feedback.</p><p>The <strong>location-sharing toggle</strong> on the matched trip card deserves a special mention. It is opt-in by design — a visually impaired user does not want their GPS broadcast by default. When the toggle is off, TalkBack announces <em>“Share my location, off, toggle”</em>. When on, it announces <em>“Share my location, on, toggle — your volunteer can now see your position”</em>. That extra context in the label isn’t fluff; for a screen reader user, it’s the entire affordance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*PGLQWwEja16aGnU2vWN0Zg.png" /></figure><h3>The Matching Engine</h3><p>When a traveler creates a trip, a <strong>PostgreSQL trigger</strong> fires immediately and runs a server-side function that scans volunteer preferences. It looks for candidates whose preferred routes, availability windows (stored as JSONB), and is_available flag all line up with the request. The first match gets an ACTIVE record. The volunteer sees it appear live in their app via a Supabase realtime channel. They accept or decline — the client never orchestrates any of this.</p><p>The core of the trigger in simplified form:</p><pre>INSERT INTO matches (trip_id, volunteer_id, vip_user_id, status)<br>SELECT NEW.id, vp.user_id, NEW.vip_user_id, &#39;ACTIVE&#39;<br>FROM volunteer_profile vp<br>WHERE vp.is_available = TRUE<br>  AND vp.preferred_routes @&gt; to_jsonb(NEW.from_station, NEW.to_station)<br>  AND availability_window_matches(vp.availability_windows, NEW.departure_time)<br>LIMIT 1;</pre><p>We ran into one memorable bug: a circular <strong>Row Level Security</strong> dependency. The policy on matches queried trip_request to verify access, and the policy on trip_request queried matches — infinite recursion, PostgreSQL error 42P17. The fix was to denormalize vip_user_id directly onto matches, so neither policy ever needs to touch the other table. A good reminder that in RLS-heavy schemas, <strong>a little denormalization is a feature, not a code smell</strong>.</p><h3>Live GPS Tracking</h3><p>Once a match is confirmed, the traveler’s device polls GPS every 10 seconds and writes coordinate rows to a locations table. The volunteer&#39;s screen fetches the last known position on load, then subscribes to new inserts in real time — so the map is accurate whether the volunteer opens it at the start of the trip or halfway through.</p><p>The subscription is handled by a single function:</p><pre>export function subscribeToMatchLocation(<br>  matchId: string,<br>  vipUserId: string,<br>  callback: (location: LocationRow) =&gt; void<br>): () =&gt; void {<br>  const channel = supabase<br>    .channel(`location:${matchId}:${vipUserId}`)<br>    .on(<br>      &#39;postgres_changes&#39;,<br>      {<br>        event: &#39;INSERT&#39;,<br>        schema: &#39;public&#39;,<br>        table: &#39;locations&#39;,<br>        filter: `match_id=eq.${matchId}`,<br>      },<br>      (payload) =&gt; {<br>        const row = payload.new as LocationRow;<br>        if (row.user_id === vipUserId) callback(row);<br>      }<br>    )<br>    .subscribe();<br><br> return () =&gt; channel.unsubscribe();<br>}</pre><p>Every new GPS insert triggers the callback, which moves the marker on the volunteer’s map. RLS ensures only the matched volunteer can read those rows — and only while the match is ACTIVE. The function returns an unsubscribe handle so the screen can clean up when the volunteer navigates away. The whole pipeline, from permission request to live marker update, is under 200 lines of TypeScript.</p><h3>Conclusion</h3><p>BlindLine is not a large app — eight database tables, a handful of Postgres functions, and a few thousand lines of TypeScript. But it solves a real coordination problem across two user types with opposing UX needs, in six languages, with live data sync and GPS, without a single dedicated backend server to maintain.</p><p>The most important lesson from this project isn’t technical. Building for a constrained user makes better software for everyone. Every accessible card grid, every carefully worded accessibilityLabel, every opt-in toggle — these decisions came from respecting the user, not chasing a design trend. The best UX choices we made were the ones we didn&#39;t have a choice about.</p><h4>Connect with us!</h4><p>Do you want to connect, ask questions or collaborate? Feel free to visit our LinkedIn profiles!</p><p><a href="https://www.linkedin.com/in/mirislom/">Mirislom M.</a><br><a href="https://www.linkedin.com/in/sebastian-gondek-7ba3633b3/">Sebastian Gondek<br></a><a href="https://www.linkedin.com/in/khalil-arinla-2b919b3a8/">Khalil Arinla</a></p><h3>References</h3><ul><li>Expo Router Documentation. (2024). <em>File-based routing for React Native</em>. <a href="https://docs.expo.dev/router/introduction/">https://docs.expo.dev/router/introduction/</a></li><li>Supabase. (2024). <em>Row Level Security</em>. <a href="https://supabase.com/docs/guides/database/postgres/row-level-security">https://supabase.com/docs/guides/database/postgres/row-level-security</a></li><li>Supabase. (2024). <em>Realtime</em>. <a href="https://supabase.com/docs/guides/realtime">https://supabase.com/docs/guides/realtime</a></li><li>Apple Inc. (2024). <em>VoiceOver</em>. <a href="https://www.apple.com/accessibility/vision/">https://www.apple.com/accessibility/vision/</a></li><li>Google. (2024). <em>TalkBack screen reader</em>. <a href="https://support.google.com/accessibility/android/answer/6007100">https://support.google.com/accessibility/android/answer/6007100</a></li><li>NMBS/SNCB. (2024). <em>Assistance for travellers with a disability</em>. <a href="https://www.belgiantrain.be/en/travel-info/prepare-for-your-journey/disabilities">https://www.belgiantrain.be/en/travel-info/prepare-for-your-journey/disabilities</a></li><li>World Health Organization. (2023). <em>Blindness and vision impairment</em>. <a href="https://www.who.int/news-room/fact-sheets/detail/blindness-and-visual-impairment">https://www.who.int/news-room/fact-sheets/detail/blindness-and-visual-impairment</a></li><li>PostgreSQL Global Development Group. (2024). <em>Row Security Policies</em>. <a href="https://www.postgresql.org/docs/current/ddl-rowsecurity.html">https://www.postgresql.org/docs/current/ddl-rowsecurity.html</a></li><li>De Markgrave. (2024). <em>Samen zien we meer</em>. <a href="https://www.demarkgrave.be/">https://www.demarkgrave.be/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70d621e3bef2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>