<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Akhil Mani</title>
    <description>The latest articles on DEV Community by Akhil Mani (@akhil_mani_df1f71f824c2bc).</description>
    <link>https://dev.to/akhil_mani_df1f71f824c2bc</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3817478%2F3d19dfc5-3609-4239-a9f3-d9fbe88faf04.png</url>
      <title>DEV Community: Akhil Mani</title>
      <link>https://dev.to/akhil_mani_df1f71f824c2bc</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/akhil_mani_df1f71f824c2bc"/>
    <language>en</language>
    <item>
      <title>Universal Health Guardian : lost GitHub account but rebuild,with Chatgpt</title>
      <dc:creator>Akhil Mani</dc:creator>
      <pubDate>Tue, 26 May 2026 00:10:02 +0000</pubDate>
      <link>https://dev.to/akhil_mani_df1f71f824c2bc/universal-health-guardian-lost-github-account-but-rebuildwith-chatgpt-48m2</link>
      <guid>https://dev.to/akhil_mani_df1f71f824c2bc/universal-health-guardian-lost-github-account-but-rebuildwith-chatgpt-48m2</guid>
      <description>&lt;p&gt;Universal Health Guardian &lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fw00y1miz51lcgk40cgyx.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fw00y1miz51lcgk40cgyx.png" alt=" " width="800" height="533"&gt;&lt;/a&gt;– &lt;/p&gt;

&lt;p&gt;Rebuilding from Scratch After Losing Everything&lt;/p&gt;

&lt;p&gt;This is a submission for the GitHub Finish-Up-A-Thon Challenge&lt;/p&gt;

&lt;p&gt;What I Built&lt;/p&gt;

&lt;p&gt;I built Universal Health Guardian (UHG) — an AI-powered healthcare assistant platform focused on helping patients and healthcare providers monitor health risks, visualize patient data, and generate predictive insights using machine learning.&lt;/p&gt;

&lt;p&gt;The project combines:&lt;/p&gt;

&lt;p&gt;A modern React dashboard UI&lt;/p&gt;

&lt;p&gt;A Node.js + Express backend&lt;/p&gt;

&lt;p&gt;PostgreSQL database architecture&lt;/p&gt;

&lt;p&gt;ML prediction endpoints&lt;/p&gt;

&lt;p&gt;Real-time health analytics concepts&lt;/p&gt;

&lt;p&gt;AI-assisted workflows powered through GitHub Copilot and vibe coding sessions&lt;/p&gt;

&lt;p&gt;The idea started as a simple healthcare dashboard experiment, but evolved into a much larger vision: a universal intelligent healthcare companion that could eventually support hospitals, remote clinics, and individual patients.&lt;/p&gt;

&lt;p&gt;Some of the core systems we built include:&lt;/p&gt;

&lt;p&gt;Patient health tracking dashboards&lt;/p&gt;

&lt;p&gt;Risk prediction APIs&lt;/p&gt;

&lt;p&gt;Medical data visualization&lt;/p&gt;

&lt;p&gt;AI-assisted recommendation flows&lt;/p&gt;

&lt;p&gt;Modular monorepo architecture for scalability&lt;/p&gt;

&lt;p&gt;Frontend-backend ML integration structure&lt;/p&gt;

&lt;p&gt;This project became more than just code for me.&lt;/p&gt;

&lt;p&gt;A major setback happened when my GitHub account got suspended unexpectedly. I lost access to years of work, repositories, experiments, and unfinished builds. I tried contacting support multiple times, but my emails never properly connected through the system.&lt;/p&gt;

&lt;p&gt;For a while, it genuinely felt like everything was gone.&lt;/p&gt;

&lt;p&gt;Instead of stopping, I started rebuilding from memory using AI-assisted development workflows and late-night vibe coding sessions. Universal Health Guardian became the comeback project that helped me regain momentum.&lt;/p&gt;




&lt;p&gt;Demo&lt;/p&gt;

&lt;p&gt;Features&lt;/p&gt;

&lt;p&gt;Interactive healthcare dashboard&lt;/p&gt;

&lt;p&gt;AI-assisted patient analytics&lt;/p&gt;

&lt;p&gt;Prediction endpoints architecture&lt;/p&gt;

&lt;p&gt;Scalable monorepo setup&lt;/p&gt;

&lt;p&gt;Responsive frontend with Tailwind CSS&lt;/p&gt;

&lt;p&gt;REST APIs for patient data and ML integration&lt;/p&gt;

&lt;p&gt;Tech Stack&lt;/p&gt;

&lt;p&gt;React 18&lt;/p&gt;

&lt;p&gt;Tailwind CSS&lt;/p&gt;

&lt;p&gt;Node.js&lt;/p&gt;

&lt;p&gt;Express.js&lt;/p&gt;

&lt;p&gt;PostgreSQL&lt;/p&gt;

&lt;p&gt;Machine Learning integration concepts&lt;/p&gt;

&lt;p&gt;GitHub Copilot&lt;/p&gt;

&lt;p&gt;AI-assisted development workflows&lt;/p&gt;

&lt;p&gt;Walkthrough&lt;/p&gt;

&lt;p&gt;Added screenshots:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Dashboard homepage&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Patient analytics panel&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;API response preview&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;System architecture diagram&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Mobile responsive view&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The Comeback Story&lt;/p&gt;

&lt;p&gt;Before this challenge, the project existed mostly across lost repositories, incomplete builds, local experiments, and AI-generated architecture drafts.&lt;/p&gt;

&lt;p&gt;When my GitHub account got suspended, I thought I had lost:&lt;/p&gt;

&lt;p&gt;My repositories&lt;/p&gt;

&lt;p&gt;Project history&lt;/p&gt;

&lt;p&gt;Previous prototypes&lt;/p&gt;

&lt;p&gt;Collaboration trails&lt;/p&gt;

&lt;p&gt;Deployment experiments&lt;/p&gt;

&lt;p&gt;Documentation&lt;/p&gt;

&lt;p&gt;That situation forced me to rethink how I build.&lt;/p&gt;

&lt;p&gt;Instead of trying to perfectly recover everything, I focused on rebuilding better:&lt;/p&gt;

&lt;p&gt;Cleaner architecture&lt;/p&gt;

&lt;p&gt;Better scalability&lt;/p&gt;

&lt;p&gt;Modular code structure&lt;/p&gt;

&lt;p&gt;Faster iteration cycles&lt;/p&gt;

&lt;p&gt;AI-assisted development&lt;/p&gt;

&lt;p&gt;Rapid prototyping workflows&lt;/p&gt;

&lt;p&gt;During this rebuild process, I used GitHub Copilot heavily alongside iterative vibe coding sessions to reconstruct systems, generate boilerplate faster, and experiment with architecture ideas rapidly.&lt;/p&gt;

&lt;p&gt;What changed during the comeback:&lt;/p&gt;

&lt;p&gt;Rebuilt frontend architecture from scratch&lt;/p&gt;

&lt;p&gt;Reorganized backend APIs&lt;/p&gt;

&lt;p&gt;Created structured ML integration endpoints&lt;/p&gt;

&lt;p&gt;Improved dashboard responsiveness&lt;/p&gt;

&lt;p&gt;Simplified deployment planning&lt;/p&gt;

&lt;p&gt;Converted scattered ideas into a more production-oriented architecture&lt;/p&gt;

&lt;p&gt;This challenge became less about “finishing an old project” and more about proving to myself that losing everything doesn’t mean starting over with nothing.&lt;/p&gt;




&lt;p&gt;My Experience with GitHub Copilot&lt;/p&gt;

&lt;p&gt;GitHub Copilot became one of the biggest reasons this rebuild moved as fast as it did.&lt;/p&gt;

&lt;p&gt;Instead of spending hours rewriting repetitive boilerplate, I used Copilot to:&lt;/p&gt;

&lt;p&gt;Generate API routes&lt;/p&gt;

&lt;p&gt;Scaffold React components&lt;/p&gt;

&lt;p&gt;Speed up backend logic creation&lt;/p&gt;

&lt;p&gt;Refactor repetitive code&lt;/p&gt;

&lt;p&gt;Prototype architecture ideas quickly&lt;/p&gt;

&lt;p&gt;Explore integration patterns faster&lt;/p&gt;

&lt;p&gt;The most valuable part wasn’t just code completion — it was momentum.&lt;/p&gt;

&lt;p&gt;After losing access to previous repositories, motivation was honestly difficult at times. Copilot helped reduce the friction between ideas and implementation. That made it easier to keep building consistently instead of getting stuck rebuilding basic foundations.&lt;/p&gt;

&lt;p&gt;Some areas where Copilot helped most:&lt;/p&gt;

&lt;p&gt;Express route generation&lt;/p&gt;

&lt;p&gt;React component scaffolding&lt;/p&gt;

&lt;p&gt;Tailwind layout structures&lt;/p&gt;

&lt;p&gt;API integration patterns&lt;/p&gt;

&lt;p&gt;Backend folder organization&lt;/p&gt;

&lt;p&gt;Rapid experimentation&lt;/p&gt;

&lt;p&gt;This project showed me how AI-assisted development can genuinely help solo builders recover faster after setbacks.&lt;/p&gt;




&lt;p&gt;Final Thoughts&lt;/p&gt;

&lt;p&gt;Universal Health Guardian is still evolving, but this Finish-Up-A-Thon pushed me to turn recovery into progress.&lt;/p&gt;

&lt;p&gt;Even after losing repositories and access to older work, rebuilding taught me:&lt;/p&gt;

&lt;p&gt;consistency matters more than perfection,&lt;/p&gt;

&lt;p&gt;momentum matters more than setbacks,&lt;/p&gt;

&lt;p&gt;and sometimes the comeback version becomes stronger than the original.&lt;/p&gt;

&lt;p&gt;If you’re rebuilding something you lost too — keep going.&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>githubchallenge</category>
      <category>ai</category>
      <category>chatgpt</category>
    </item>
    <item>
      <title>The Android Spam shield</title>
      <dc:creator>Akhil Mani</dc:creator>
      <pubDate>Wed, 20 May 2026 11:22:51 +0000</pubDate>
      <link>https://dev.to/akhil_mani_df1f71f824c2bc/the-android-spam-shield-824</link>
      <guid>https://dev.to/akhil_mani_df1f71f824c2bc/the-android-spam-shield-824</guid>
      <description>&lt;p&gt;Trust First, Customers Later: Building the Android "Spam Shield" with Antigravity 2.0 and Android 17&lt;/p&gt;

&lt;p&gt;A Personal Journey from Being Spammed to Building a Shield&lt;/p&gt;

&lt;p&gt;The moment you sign up for a service, buy a new device, or share your number, it begins. The spam. I lived through this firsthand when a toxic client weaponized my information. It didn’t just feel like an annoyance; it felt like a violation of my digital sovereignty."&lt;br&gt;
​For too long, big tech's motto has been "Growth first, privacy later." It's time to flip the script. Our new architectural philosophy is simple: Trust first, customer later.&lt;br&gt;
​Watching the Google I/O 2026 keynotes, I realized that we finally have the tech stack required to move from passive call-blocking to active, autonomous defense. This is the story of how we can combine Android 17, Antigravity 2.0, and Gemini 3.5 Flash to build an aggressive, built-in Spam Shield that doesn't just block spammers—it hunts them, references a global database, and hands their data straight to law enforcement.&lt;/p&gt;

&lt;p&gt;The 3-Tier "Spam Shield" Architecture&lt;br&gt;
​To completely lock down a Pixel or Android device, we have to synthesize three massive announcements from I/O 2026 into a single cohesive system:&lt;/p&gt;

&lt;p&gt;[Android 17 OS Layer] -&amp;gt; [Antigravity 2.0 Global DB Check] -&amp;gt; [Gemini 3.5 Flash Agent] -&amp;gt; [Automated Legal Report]&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The Gatekeeper: Android 17 OS Verification
​Instead of waiting for a spammer to text or call, Android 17's new deep OS verification and integrity APIs ensure that unverified apps, emulators, or bot-farm clones cannot even execute background tasks on the device network. If an incoming communication doesn't pass cryptographic verification, it's flagged instantly before it can scrape user data.
​2. The Brain: Antigravity 2.0 &amp;amp; Gemini 3.5 Flash Sub-Agents
​When a suspicious interaction bypasses basic filters, an isolated Antigravity 2.0 agent is spun up instantly. Leveraging the mind-boggling speed of Gemini 3.5 Flash (clocking in at 289 output tokens/sec), the agent cross-references the spammer's metadata against Google's global security database in milliseconds.
​Because Antigravity 2.0 allows agents to spawn independent, asynchronous sub-agents on the fly, one sub-agent can seamlessly isolate the spammer in a virtual sandbox while another handles data compilation.
​3. The Hammer: Automated Law Enforcement Reporting
​If the global database or the Gemini model flags the entity as a malicious spammer/scammer with a probability score greater than 95%, the shield triggers an automated legal reporting pipeline. Using secure JSON hooks, it compiles the spammer's IP header, carrier routing info, and payload, generating a standardized report sent directly to local cyber security teams or federal law enforcement (like the FBI's IC3 portal).&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;​The Code Blueprint: The Asynchronous Spam Handler&lt;br&gt;
​Here is a conceptual look at how an Antigravity 2.0 agent script handles a flagged interaction using the new /goal directive to run an enforcement pipeline to completion:&lt;/p&gt;

&lt;p&gt;// Antigravity 2.0 Autonomous Spam Shield Hook&lt;br&gt;
import { googleSecurityDB, lawEnforcementAPI } from '@google/android17-security';&lt;br&gt;
import { Gemini35Flash } from '@google/vertex-ai';&lt;/p&gt;

&lt;p&gt;export async function onSuspiciousInteractionTrigger(interaction) {&lt;br&gt;
  // Step 1: Query Google's Real-time Database&lt;br&gt;
  const isFlagged = await googleSecurityDB.checkEntity(interaction.senderMetadata);&lt;/p&gt;

&lt;p&gt;if (isFlagged || interaction.trustScore &amp;lt; 0.05) {&lt;br&gt;
    console.log("Spammer detected. Initiating 'Trust First' protocol.");&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;// Step 2: Spin up a Gemini 3.5 Flash Agent to analyze intent and compile evidence
const analysis = await Gemini35Flash.analyzePayload({
  content: interaction.payload,
  systemInstruction: "Extract routing, headers, and malicious intent indicators."
});

// Step 3: Trigger automated law enforcement pipeline asynchronously
await lawEnforcementAPI.submitCyberCrimeReport({
  evidence: analysis.extractedData,
  routingDetails: interaction.networkHeaders,
  classification: "Automated Mass Spam / Data Harvesting"
});

// Step 4: Vaporize the data trail on the user's local device
await interaction.blockAndPurge();
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;}&lt;br&gt;
}&lt;/p&gt;

&lt;p&gt;Why This Matters for the Future of Humanity&lt;br&gt;
When we protect a Google user, we shouldn't just minimize a notification; we should actively dismantle the spammer's infrastructure. By forcing their data back into law enforcement databases the second they hit a honeypot, we make spamming too legally and financially risky to sustain.&lt;br&gt;
Software development shouldn't just be about building cooler apps; it should be about building an ecosystem where everyday users feel entirely safe. Let's build a web where trust isn't a premium feature—it's the baseline.&lt;br&gt;
Disclaimer: This post is a submission for the Google I/O 2026 Writing Challenge. I used Gemini to help synthesize my personal experience and architectural ideas into this final written piece.&lt;/p&gt;

&lt;p&gt;Hope google users would be saved from the project we are building...&lt;br&gt;
Soon in playstore free for all..&lt;/p&gt;

&lt;p&gt;&lt;a href="https://youtube.com/shorts/s4TdWLdX4rc?si=_4OFty8-Qvq9DuoD" rel="noopener noreferrer"&gt;https://youtube.com/shorts/s4TdWLdX4rc?si=_4OFty8-Qvq9DuoD&lt;/a&gt;&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>googleiochallenge</category>
      <category>actionshackathon</category>
      <category>mobile</category>
    </item>
  </channel>
</rss>
