{"version":"https://jsonfeed.org/version/1.1","title":"Engineer — Support — Portfolio and notes","home_page_url":"https://support.engineer.company/","feed_url":"https://support.engineer.company/feed.json","description":"Engineer ApS — software development \u0026 IT consulting in Copenhagen, Denmark. A portfolio of proven engineering achievements across software, data, cloud and IT.","language":"en","icon":"https://support.engineer.company/assets/images/brand/card.webp","favicon":"https://support.engineer.company/assets/icons/apple/apple-touch-icon.png","authors":[{"name":"Engineer ApS","url":"https://support.engineer.company/"}],"items":[{"id":"https://support.engineer.company/portfolio/established-a-technical-support-department-servicing-over-10-40/","url":"https://support.engineer.company/portfolio/established-a-technical-support-department-servicing-over-10-40/","title":"Established a Technical Support department, servicing over 10,000 clients with IT support and troubleshooting solutions.","summary":"Established a Technical Support department serving 10,000+ clients, turning support from reactive fixes into a scalable company strength.","content_html":"\u003cp\u003e\u003cstrong\u003eSituation.\u003c/strong\u003e The client base was growing and needed dependable technical support, and there just wasn\u0026rsquo;t a dedicated function to give it to them at any real scale. Support was happening ad hoc, which works for a handful of clients and quietly falls apart as the numbers climb.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eTask.\u003c/strong\u003e Standing up an actual technical‑support capability — one that could serve a large and still‑growing client base — was the job.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eAction.\u003c/strong\u003e A Technical Support department got built from nothing. That meant deciding how it would actually work before hiring into it — the process for how a request came in and got resolved, the tooling to handle volume, the standard for what good support looked like — and then building the capacity to deliver IT support and troubleshooting to a lot of clients at once. Starting from scratch was the advantage, honestly; it could be designed for the scale the company was heading toward instead of patching something that had grown up by accident.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eResult.\u003c/strong\u003e The department ended up serving over ten thousand clients with reliable support and troubleshooting. Support went from a thing done reactively to a genuine strength of the company — something that scaled with the client base instead of buckling under it.\u003c/p\u003e\n","date_published":"2026-09-13T01:45:50+02:00","date_modified":"2026-09-13T01:45:50+02:00","language":"en","tags":["Mentoring \u0026 Coaching","Product \u0026 Requirements","Project Management","Stakeholder \u0026 Reporting","System Administration","Team Leadership","IT Support \u0026 Helpdesk","Project Management (Agile)","Team Building \u0026 Mentoring"]},{"id":"https://support.engineer.company/portfolio/managed-a-team-delivering-it-support-data-recovery-47/","url":"https://support.engineer.company/portfolio/managed-a-team-delivering-it-support-data-recovery-47/","title":"Managed a team delivering IT support, data recovery, and hardware repair services to over 1,000 clients, ensuring high‑quality service.","summary":"Led a team delivering IT support, data recovery and hardware repair to 1,000+ clients, building a reputation for reliable service.","content_html":"\u003cp\u003e\u003cstrong\u003eSituation.\u003c/strong\u003e The company was the place a large base of clients came to when their IT broke — support, data recovery, hardware repair, the full spread. Meeting that kind of steady, unglamorous demand isn\u0026rsquo;t about heroics; it\u0026rsquo;s about having a team that runs well day after day, because the work never really stops coming.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eTask.\u003c/strong\u003e Managing the team that delivered all that was the job, and keeping the quality consistent whether it was a quiet week or everything arriving at once.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eAction.\u003c/strong\u003e The team ran IT support, data recovery and hardware repair for over a thousand clients. A lot of that was the organising underneath — making sure work got picked up and not dropped, setting a standard for what \u0026ldquo;fixed\u0026rdquo; actually meant so people weren\u0026rsquo;t getting half‑repairs back, and keeping the team effective when the queue was long. Data recovery especially is work you can\u0026rsquo;t be casual about; it\u0026rsquo;s usually someone\u0026rsquo;s photos or their business sitting on that drive, and they\u0026rsquo;re already having a bad day by the time they reach you.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eResult.\u003c/strong\u003e The team served over a thousand clients and built a real reputation for reliable service. In that kind of business the reputation is everything — people come back, and they tell others, precisely because the last time something broke you actually sorted it.\u003c/p\u003e\n","date_published":"2026-09-13T01:45:50+02:00","date_modified":"2026-09-13T01:45:50+02:00","language":"en","tags":["Mentoring \u0026 Coaching","Stakeholder \u0026 Reporting","System Administration","Team Leadership","Hardware Repair \u0026 Data Recovery","IT Support \u0026 Helpdesk","Team Building \u0026 Mentoring"]},{"id":"https://support.engineer.company/portfolio/configured-and-deployed-1-000-wi-fi-routers-48/","url":"https://support.engineer.company/portfolio/configured-and-deployed-1-000-wi-fi-routers-48/","title":"Configured and deployed 1,000 Wi‑Fi routers, improving network accessibility and performance for clients.","summary":"Configured and deployed 1,000 Wi-Fi routers with a standard setup, giving clients dependable wireless access and performance.","content_html":"\u003cp\u003e\u003cstrong\u003eSituation.\u003c/strong\u003e Clients needed wireless that just worked, and that came down to configuring and rolling out a large number of Wi‑Fi routers — and doing it the same careful way every time, because a router set up sloppily is either insecure or slow, and usually you find out which one later.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eTask.\u003c/strong\u003e Configuring and deploying those routers to give clients better network access and performance was the job.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eAction.\u003c/strong\u003e A thousand Wi‑Fi routers got configured and deployed. The trick at that number is standardising the setup — a consistent, secure, sensible configuration — rather than tuning each one from scratch on the day, because a thousand hand‑crafted routers is a thousand different things to support later. So they were set up for security and performance the same way each time, and rolled out reliably across client sites.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eResult.\u003c/strong\u003e The thousand routers gave clients dependable wireless — better access, better performance — and did it consistently, because the setup was standard rather than improvised. A router nobody has to think about again is the goal; most of these got there.\u003c/p\u003e\n","date_published":"2026-09-13T01:45:50+02:00","date_modified":"2026-09-13T01:45:50+02:00","language":"en","tags":["Infrastructure","Networking \u0026 VPN","Reliability \u0026 Backups","Security","System Administration","IT Support \u0026 Helpdesk","Networking \u0026 VPN Setup"]},{"id":"https://support.engineer.company/portfolio/managed-4-000-computer-repairs-ensuring-rapid-and-49/","url":"https://support.engineer.company/portfolio/managed-4-000-computer-repairs-ensuring-rapid-and-49/","title":"Managed 4,000 computer repairs, ensuring rapid and effective resolution of hardware and software issues.","summary":"Handled 4,000 computer repairs with fast, effective resolution of hardware and software issues, upholding a name for dependable service.","content_html":"\u003cp\u003e\u003cstrong\u003eSituation.\u003c/strong\u003e There was a constant stream of computer repairs coming through — four thousand of them over time — and every one was someone waiting to get their machine back and get on with their day. Hardware faults, software faults, the whole mix, and clients judged the shop on how fast and how properly they got fixed.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eTask.\u003c/strong\u003e Managing those repairs was the job — keeping problems getting resolved quickly and, just as importantly, correctly.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eAction.\u003c/strong\u003e Four thousand computer repairs went through — diagnosing the hardware and software faults, organising the workflow so machines moved through instead of piling up, and holding the quality so a repair was actually done right rather than sent back out to fail again next week. A repair that comes back is worse than a slow one; it costs the client a second trip and costs the shop the trust. So the throughput mattered, but never at the expense of fixing it the first time.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eResult.\u003c/strong\u003e All four thousand got resolved, and quickly. People got their machines back working and got on with things, and the company\u0026rsquo;s name for dependable service held up — which in a repair shop is the whole business.\u003c/p\u003e\n","date_published":"2026-09-13T01:45:50+02:00","date_modified":"2026-09-13T01:45:50+02:00","language":"en","tags":["System Administration","Hardware Repair \u0026 Data Recovery","IT Support \u0026 Helpdesk"]},{"id":"https://support.engineer.company/portfolio/provided-round-the-clock-24-7-infrastructure-support-82/","url":"https://support.engineer.company/portfolio/provided-round-the-clock-24-7-infrastructure-support-82/","title":"Provided round‑the‑clock 24/7 infrastructure support for an IPTV/OTT streaming platform, administering ~1,000 servers plus client‑owned systems for global customers in China, the US and Germany.","summary":"Provided 24/7 infrastructure support for an IPTV/OTT streaming platform — ~1,000 servers plus client systems across China, the US and Germany.","content_html":"\u003cp\u003e\u003cstrong\u003eSituation.\u003c/strong\u003e This was an IPTV/OTT streaming platform with customers spread across China, the US and Germany, which meant there was no quiet hour to do maintenance in — someone, somewhere, was always watching. Downtime on a platform like that isn\u0026rsquo;t an abstract metric; it\u0026rsquo;s someone\u0026rsquo;s television just stopping, and they don\u0026rsquo;t care why.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eTask.\u003c/strong\u003e Keeping the platform\u0026rsquo;s infrastructure available around the clock was the job — genuinely around the clock, not \u0026ldquo;business hours plus an on‑call rota nobody answers.\u0026rdquo;\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eAction.\u003c/strong\u003e 24/7 support ran for roughly a thousand servers, plus a good number of client‑owned systems on top of that — administering them, monitoring them, keeping them secured and configured across the whole streaming estate. Because customers sat in three very different time zones, \u0026ldquo;after hours\u0026rdquo; didn\u0026rsquo;t really exist; a problem at 3am local was primetime for someone else, so it got treated as primetime. A lot of the work was noticing something drifting before it became an outage, because on a live streaming platform you don\u0026rsquo;t get to fix things quietly after the fact.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eResult.\u003c/strong\u003e The platform stayed continuously available for a global audience, with problems caught and dealt with at whatever hour they turned up, before they reached a viewer\u0026rsquo;s screen. On a 24/7 service that\u0026rsquo;s the whole job — success looks like nothing happening, which is exactly what the viewers wanted.\u003c/p\u003e\n","date_published":"2026-09-13T01:45:50+02:00","date_modified":"2026-09-13T01:45:50+02:00","language":"en","tags":["Cloud","Infrastructure","Linux \u0026 Servers","Monitoring \u0026 Observability","Networking \u0026 VPN","Reliability \u0026 Backups","System Administration","IT Support \u0026 Helpdesk","Site Reliability \u0026 Monitoring"]},{"id":"https://support.engineer.company/portfolio/performed-data-recovery-across-a-wide-range-of-92/","url":"https://support.engineer.company/portfolio/performed-data-recovery-across-a-wide-range-of-92/","title":"Performed data recovery across a wide range of media — SD cards, HDDs, SSDs, RAID arrays, external drives and Mac systems.","summary":"Recovered critical data across SD cards, HDDs, SSDs, RAID arrays, external drives and Mac systems — files back from devices written off as lost.","content_html":"\u003cp\u003e\u003cstrong\u003eSituation.\u003c/strong\u003e People turned up with storage that had failed or been damaged, and data on it they urgently needed back — and by the time someone\u0026rsquo;s carrying a dead drive into a shop, they\u0026rsquo;re usually past worried and into panicking. Photos, business files, the only copy of something that mattered.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eTask.\u003c/strong\u003e Recovering their data, across whatever media they walked in with, was the job.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eAction.\u003c/strong\u003e Data recovery ran across pretty much every common storage type — SD cards, spinning HDDs, SSDs, RAID arrays, external drives, Mac systems. Each of those fails and gives up its data differently: an SSD is a different problem from a platter drive, a RAID array is a different problem again, and a Mac filesystem has its own quirks. So the work was as much about knowing the right approach for the specific medium as it was about any single technique.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eResult.\u003c/strong\u003e Clients got critical data back from devices they\u0026rsquo;d already written off as gone, across every common kind of storage. There\u0026rsquo;s a specific relief on someone\u0026rsquo;s face when you hand back the drive with their files intact — that was the point of the work, and it happened across the whole range of media.\u003c/p\u003e\n","date_published":"2026-09-13T01:45:50+02:00","date_modified":"2026-09-13T01:45:50+02:00","language":"en","tags":["Reliability \u0026 Backups","System Administration","Hardware Repair \u0026 Data Recovery","IT Support \u0026 Helpdesk"]},{"id":"https://support.engineer.company/portfolio/diagnosed-and-repaired-laptop-hardware-screens-hinges-keyboards-93/","url":"https://support.engineer.company/portfolio/diagnosed-and-repaired-laptop-hardware-screens-hinges-keyboards-93/","title":"Diagnosed and repaired laptop hardware — screens, hinges, keyboards, trackpads, motherboards and power — and resolved software issues across Linux, Windows and Mac.","summary":"Diagnosed and repaired laptop hardware — screens, hinges, keyboards, trackpads, motherboards, power — and fixed software on Linux, Windows and Mac.","content_html":"\u003cp\u003e\u003cstrong\u003eSituation.\u003c/strong\u003e Laptops came in with the full range of things that go wrong with laptops — cracked screens, broken hinges, dead keyboards, failing trackpads, motherboard faults, power problems — plus the software side, across Linux, Windows and Mac. Basically, whatever was wrong with it, it landed on the bench.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eTask.\u003c/strong\u003e Diagnosing and fixing them reliably was the job — reliably being the operative word, because a laptop repair that doesn\u0026rsquo;t hold is just a delayed second visit.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eAction.\u003c/strong\u003e The hardware was repaired end to end — screens, hinges, keyboards, trackpads, motherboards, power — which at the motherboard level is genuinely fiddly, close work, and the software problems resolved across all three operating systems. The diagnosis is usually the real skill: a laptop that won\u0026rsquo;t power on could be the charger, the board, or the battery, and the repair is only as good as the guess about what\u0026rsquo;s actually broken. So the care went into finding the real fault before touching anything.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eResult.\u003c/strong\u003e Machines went back to their owners working and dependable, hardware and software both sorted. A repair that holds up is the only kind worth doing, and getting the diagnosis right first is what made these hold.\u003c/p\u003e\n","date_published":"2026-09-13T01:45:50+02:00","date_modified":"2026-09-13T01:45:50+02:00","language":"en","tags":["Linux \u0026 Servers","Reliability \u0026 Backups","System Administration","Hardware Repair \u0026 Data Recovery","IT Support \u0026 Helpdesk"]},{"id":"https://support.engineer.company/notes/solana-mobile-wallet-deeplinks/","url":"https://support.engineer.company/notes/solana-mobile-wallet-deeplinks/","title":"Opening a dApp inside Solana mobile wallets","summary":"Why Phantom, Solflare and Backpack browse deep links fail on mobile, and the exact formats, trigger rules and fixes that make them work.","content_html":"\u003cp\u003eA React dApp built on \u003ccode\u003e@solana/wallet-adapter-react\u003c/code\u003e connects desktop wallets\nwithout trouble, but on a phone the same flow falls apart: the wallet has to\nopen the dApp inside its own in-app browser, and the deep links that should\nmake that happen quietly do not. Backpack lands on a \u0026ldquo;download the app\u0026rdquo; page;\nSolflare opens the app but never the site; every variant seems to fail. We took\nthe problem apart, and it turned out to be four separate problems wearing one\nsymptom.\u003c/p\u003e\n\u003ch2 id=\"the-four-problems\"\u003eThe four problems\u003c/h2\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eThe Backpack link was malformed.\u003c/strong\u003e The only documented format is\n\u003ccode\u003ehttps://backpack.app/ul/v1/browse/\u0026lt;url\u0026gt;?ref=\u0026lt;ref\u0026gt;\u003c/code\u003e — a universal link with\nthe target URL in the path and a required \u003ccode\u003eref\u003c/code\u003e. A custom-scheme guess like\n\u003ccode\u003ebackpack://ul/v1/browse?url=...\u003c/code\u003e matches no route the app registers, so the\nuser ends on the wallet\u0026rsquo;s install page.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSolflare needs its universal link too:\u003c/strong\u003e\n\u003ccode\u003ehttps://solflare.com/ul/v1/browse/\u0026lt;url\u0026gt;?ref=\u0026lt;ref\u0026gt;\u003c/code\u003e, not the bare\n\u003ccode\u003esolflare://\u003c/code\u003e scheme. A bare scheme can launch the app without routing it —\nwhich is exactly \u0026ldquo;the app opens, but the site tab has to be opened by hand\u0026rdquo;.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBoth parameters must be encoded.\u003c/strong\u003e \u003ccode\u003eurl\u003c/code\u003e is the full absolute dApp address\nand \u003ccode\u003eref\u003c/code\u003e is the requesting origin, each passed through \u003ccode\u003eencodeURIComponent\u003c/code\u003e.\nAn unencoded \u003ccode\u003e?\u003c/code\u003e or \u003ccode\u003e\u0026amp;\u003c/code\u003e in the target corrupts the parse, and the wallet\nopens on its home screen instead of the browser tab.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eThe trigger matters as much as the link.\u003c/strong\u003e Universal links only switch apps\non a navigation the operating system trusts — and they deliberately do\nnothing when pasted into the address bar, which is also how a perfectly\ncorrect link \u0026ldquo;fails\u0026rdquo; during testing.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"the-documented-formats\"\u003eThe documented formats\u003c/h2\u003e\n\n\u003cul\u003e\n\u003cli\u003ePhantom: \u003ccode\u003ehttps://phantom.app/ul/browse/\u0026lt;url\u0026gt;?ref=\u0026lt;ref\u0026gt;\u003c/code\u003e — no \u003ccode\u003e/v1\u003c/code\u003e in this\none.\u003c/li\u003e\n\u003cli\u003eSolflare: \u003ccode\u003ehttps://solflare.com/ul/v1/browse/\u0026lt;url\u0026gt;?ref=\u0026lt;ref\u0026gt;\u003c/code\u003e\u003c/li\u003e\n\u003cli\u003eBackpack: \u003ccode\u003ehttps://backpack.app/ul/v1/browse/\u0026lt;url\u0026gt;?ref=\u0026lt;ref\u0026gt;\u003c/code\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eOne pattern serves all three:\u003c/p\u003e\n\u003cpre tabindex=\"0\"\u003e\u003ccode\u003econst WALLET_BROWSE = {\n  phantom: (url, ref) =\u0026gt;\n    `https://phantom.app/ul/browse/${url}?ref=${ref}`,\n  solflare: (url, ref) =\u0026gt;\n    `https://solflare.com/ul/v1/browse/${url}?ref=${ref}`,\n  backpack: (url, ref) =\u0026gt;\n    `https://backpack.app/ul/v1/browse/${url}?ref=${ref}`,\n};\n\nfunction walletBrowseLink(\n  walletName,\n  targetUrl = window.location.href,\n) {\n  const build = WALLET_BROWSE[walletName.toLowerCase()];\n  if (!build) return null;\n  return build(\n    encodeURIComponent(targetUrl),\n    encodeURIComponent(window.location.origin),\n  );\n}\n\u003c/code\u003e\u003c/pre\u003e\u003ch2 id=\"triggering-the-link-so-ios-and-android-accept-it\"\u003eTriggering the link so iOS and Android accept it\u003c/h2\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRender a real anchor, precomputed.\u003c/strong\u003e A plain\n\u003ccode\u003e\u0026lt;a href={walletBrowseLink('phantom')}\u0026gt;\u003c/code\u003e is the most reliable trigger on both\nplatforms.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eIf it must be programmatic\u003c/strong\u003e, assign \u003ccode\u003ewindow.location.href\u003c/code\u003e synchronously\ninside the tap handler — no \u003ccode\u003eawait\u003c/code\u003e, no \u003ccode\u003efetch\u003c/code\u003e, no \u003ccode\u003esetTimeout\u003c/code\u003e first. After\nasynchronous work the gesture context is gone, and iOS falls back to the\nwallet\u0026rsquo;s website. Never \u003ccode\u003ewindow.open\u003c/code\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNever test by pasting into the address bar.\u003c/strong\u003e Universal links deliberately\ndo not fire there; test with a tapped link or a QR code scanned by the\ncamera.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMind the messenger webviews.\u003c/strong\u003e Opened inside Telegram\u0026rsquo;s or Instagram\u0026rsquo;s\nin-app browser, universal links are frequently swallowed and the wallet\u0026rsquo;s\nplain website loads instead. User-agent detection is heuristic at best, so\nalso give users a visible escape hatch: \u0026ldquo;open in Safari or Chrome, then\nconnect\u0026rdquo;.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"the-bigger-fix-on-android\"\u003eThe bigger fix on Android\u003c/h2\u003e\n\n\u003cp\u003eHand-rolled deep links are the iOS story. On Android, Solana Mobile\u0026rsquo;s Mobile\nWallet Adapter lets a dApp running in the mobile browser connect straight to\nthe installed wallet app, with no in-app-browser detour at all. Recent versions\nof \u003ccode\u003e@solana/wallet-adapter-react\u003c/code\u003e register the mobile adapter automatically, so\nupgrading the wallet-adapter packages can fix Android by itself. The target\narchitecture: Mobile Wallet Adapter on Android, browse universal links on iOS,\nwhere Apple allows no equivalent.\u003c/p\u003e\n\u003ch2 id=\"verifying-on-a-device\"\u003eVerifying on a device\u003c/h2\u003e\n\n\u003col\u003e\n\u003cli\u003eReal device, wallet installed, link opened from the system browser — not\nfrom a messenger.\u003c/li\u003e\n\u003cli\u003eTap a rendered link or scan a QR code; never paste into the address bar.\u003c/li\u003e\n\u003cli\u003eConfirm the wallet opens and the dApp loads in its in-app browser tab — the\nsecond half is the part that fails.\u003c/li\u003e\n\u003cli\u003eRepeat without the wallet installed: the universal link should degrade to\nthe wallet\u0026rsquo;s website. That page appearing while the app is installed means\nthe link or the trigger is still wrong.\u003c/li\u003e\n\u003cli\u003eThen test the messenger path, and add the \u0026ldquo;open in browser\u0026rdquo; hint if it\nfails there.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"sources\"\u003eSources\u003c/h2\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"https://docs.phantom.com/phantom-deeplinks/deeplinks-ios-and-android\"\u003ePhantom: deep links on iOS and Android\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://docs.solflare.com/solflare/technical/deeplinks/other-methods/browse\"\u003eSolflare: the Browse deep link\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://docs.backpack.app/deeplinks/other-methods/browse\"\u003eBackpack: the Browse deep link\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://docs.solanamobile.com/mobile-wallet-adapter/mobile-apps\"\u003eSolana Mobile: Mobile Wallet Adapter\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n","date_published":"2026-08-10T00:00:00Z","date_modified":"2026-09-13T01:45:50+02:00","language":"en"}]}