The Problem
A returning client running a QR Code Downloader tool — which takes a Google Drive link and generates a downloadable QR code PDF — needed frontend bugs fixed alongside backend work involving Google authentication, which had proven tricky to get right on their own.
The Solution
I fixed the frontend issues affecting the tool's Google Drive link input and QR PDF download flow, and handled the Google authentication work on the backend that the client specifically needed help with. This was a repeat engagement — I'd worked with this client before — so the fixes built on an existing understanding of their system rather than starting from zero.
Key Features
Google Drive link input — accepts a Google Drive link as the source for QR code generation.
QR PDF generation & download — converts the input link into a downloadable QR code PDF.
Google authentication handling — backend authentication against Google's APIs, fixed to work reliably rather than intermittently.
Technical Highlights
The trickiest part of this engagement, per the client's own description, was "intricate Google authentication" on the backend — the kind of OAuth/API-key configuration work that's easy to get subtly wrong (scopes, token refresh, redirect URIs) and hard to debug without real experience with Google's authentication flows. Frontend fixes were made alongside this to keep the tool's actual user-facing flow working correctly.
Results
Delivered within a 1–7 day turnaround for $50–$100, with a 5-star review from a returning client: "I had the pleasure of working with Yasir once again, and he consistently impresses me with his expertise. Whether tackling frontend tasks or handling intricate Google authentication for our backend, his skills are top-notch. I look forward to continuing our collaboration and would highly recommend him to anyone in need of a talented freelancer."
FAQ
What does the QR Code Downloader tool actually do?
It takes a Google Drive link as input and generates a downloadable QR code PDF from it — so scanning the QR code leads to that Drive file or link.
What was specifically difficult about the Google authentication work?
Google's OAuth and API authentication flows involve configuration details — scopes, token refresh, redirect URIs — that are easy to get subtly wrong and hard to diagnose without direct experience debugging them, which is why the client called it out specifically as "intricate."
Was this a one-off job or ongoing work?
A repeat engagement — the client had worked with me before and returned for this round of frontend and authentication fixes, and mentioned wanting to continue the collaboration going forward.
How long did this take?
1–7 days, delivered through Fiverr for a $50–$100 price range.
Is there a client reference for this work?
Yes — a verified 5-star Fiverr review: "I had the pleasure of working with Yasir once again, and he consistently impresses me with his expertise... his skills are top-notch."
