<?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: vinnugollakoti</title>
    <description>The latest articles on DEV Community by vinnugollakoti (@vinnugollakoti).</description>
    <link>https://dev.to/vinnugollakoti</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2574960%2Faadc7583-192d-424b-b8a4-27012bce818f.png</url>
      <title>DEV Community: vinnugollakoti</title>
      <link>https://dev.to/vinnugollakoti</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vinnugollakoti"/>
    <language>en</language>
    <item>
      <title>Wants to know about Best AI Chatbot Widget in 2026 ?</title>
      <dc:creator>vinnugollakoti</dc:creator>
      <pubDate>Fri, 12 Jun 2026 14:51:22 +0000</pubDate>
      <link>https://dev.to/vinnugollakoti/wants-to-know-about-best-ai-chatbot-widget-in-2026--2pd5</link>
      <guid>https://dev.to/vinnugollakoti/wants-to-know-about-best-ai-chatbot-widget-in-2026--2pd5</guid>
      <description>&lt;div class="ltag__link--embedded"&gt;
  &lt;div class="crayons-story "&gt;
  &lt;a href="https://dev.to/vinnugollakoti/best-ai-chatbot-widget-2026-3598" class="crayons-story__hidden-navigation-link"&gt;Best AI Chatbot Widget 2026&lt;/a&gt;


  &lt;div class="crayons-story__body crayons-story__body-full_post"&gt;
    &lt;div class="crayons-story__top"&gt;
      &lt;div class="crayons-story__meta"&gt;
        &lt;div class="crayons-story__author-pic"&gt;

          &lt;a href="/vinnugollakoti" class="crayons-avatar  crayons-avatar--l  "&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%2Fuser%2Fprofile_image%2F2574960%2Faadc7583-192d-424b-b8a4-27012bce818f.png" alt="vinnugollakoti profile" class="crayons-avatar__image"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
        &lt;div&gt;
          &lt;div&gt;
            &lt;a href="/vinnugollakoti" class="crayons-story__secondary fw-medium m:hidden"&gt;
              vinnugollakoti
            &lt;/a&gt;
            &lt;div class="profile-preview-card relative mb-4 s:mb-0 fw-medium hidden m:inline-block"&gt;
              
                vinnugollakoti
                
              
              &lt;div id="story-author-preview-content-3883835" class="profile-preview-card__content crayons-dropdown branded-7 p-4 pt-0"&gt;
                &lt;div class="gap-4 grid"&gt;
                  &lt;div class="-mt-4"&gt;
                    &lt;a href="/vinnugollakoti" class="flex"&gt;
                      &lt;span class="crayons-avatar crayons-avatar--xl mr-2 shrink-0"&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%2Fuser%2Fprofile_image%2F2574960%2Faadc7583-192d-424b-b8a4-27012bce818f.png" class="crayons-avatar__image" alt=""&gt;
                      &lt;/span&gt;
                      &lt;span class="crayons-link crayons-subtitle-2 mt-5"&gt;vinnugollakoti&lt;/span&gt;
                    &lt;/a&gt;
                  &lt;/div&gt;
                  &lt;div class="print-hidden"&gt;
                    
                      Follow
                    
                  &lt;/div&gt;
                  &lt;div class="author-preview-metadata-container"&gt;&lt;/div&gt;
                &lt;/div&gt;
              &lt;/div&gt;
            &lt;/div&gt;

          &lt;/div&gt;
          &lt;a href="https://dev.to/vinnugollakoti/best-ai-chatbot-widget-2026-3598" class="crayons-story__tertiary fs-xs"&gt;&lt;time&gt;Jun 12&lt;/time&gt;&lt;span class="time-ago-indicator-initial-placeholder"&gt;&lt;/span&gt;&lt;/a&gt;
        &lt;/div&gt;
      &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class="crayons-story__indention"&gt;
      &lt;h2 class="crayons-story__title crayons-story__title-full_post"&gt;
        &lt;a href="https://dev.to/vinnugollakoti/best-ai-chatbot-widget-2026-3598" id="article-link-3883835"&gt;
          Best AI Chatbot Widget 2026
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;div class="crayons-story__tags"&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/ai"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;ai&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/webdev"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;webdev&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/widgets"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;widgets&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/productivity"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;productivity&lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="crayons-story__bottom"&gt;
        &lt;div class="crayons-story__details"&gt;
          &lt;a href="https://dev.to/vinnugollakoti/best-ai-chatbot-widget-2026-3598" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left"&gt;
            &lt;div class="multiple_reactions_aggregate"&gt;
              &lt;span class="multiple_reactions_icons_container"&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/exploding-head-daceb38d627e6ae9b730f36a1e390fca556a4289d5a41abb2c35068ad3e2c4b5.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/multi-unicorn-b44d6f8c23cdd00964192bedc38af3e82463978aa611b4365bd33a0f1f4f3e97.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
              &lt;/span&gt;
              &lt;span class="aggregate_reactions_counter"&gt;5&lt;span class="hidden s:inline"&gt;&amp;nbsp;reactions&lt;/span&gt;&lt;/span&gt;
            &lt;/div&gt;
          &lt;/a&gt;
            &lt;a href="https://dev.to/vinnugollakoti/best-ai-chatbot-widget-2026-3598#comments" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left flex items-center"&gt;
              

              &lt;span class="hidden s:inline"&gt;Add&amp;nbsp;Comment&lt;/span&gt;
            &lt;/a&gt;
        &lt;/div&gt;
        &lt;div class="crayons-story__save"&gt;
          &lt;small class="crayons-story__tertiary fs-xs mr-2"&gt;
            3 min read
          &lt;/small&gt;
            
              &lt;span class="bm-initial crayons-icon c-btn__icon"&gt;
                

              &lt;/span&gt;
              &lt;span class="bm-success crayons-icon c-btn__icon"&gt;
                

              &lt;/span&gt;
            
        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;


</description>
    </item>
    <item>
      <title>Best AI Chatbot Widget 2026</title>
      <dc:creator>vinnugollakoti</dc:creator>
      <pubDate>Fri, 12 Jun 2026 14:49:49 +0000</pubDate>
      <link>https://dev.to/vinnugollakoti/best-ai-chatbot-widget-2026-3598</link>
      <guid>https://dev.to/vinnugollakoti/best-ai-chatbot-widget-2026-3598</guid>
      <description>&lt;h2&gt;
  
  
  Best AI Chatbot Widget for Websites in 2026: &lt;strong&gt;Lioric&lt;/strong&gt;
&lt;/h2&gt;

&lt;h2&gt;
  
  
  Why Lioric is My #1 Choice
&lt;/h2&gt;

&lt;p&gt;In 2026, every e-commerce store, SaaS landing page, and service website needs a smart AI assistant. But most solutions are either too expensive, too complex, or give generic answers that frustrate users.&lt;/p&gt;

&lt;p&gt;After testing dozens of tools, I built and now strongly recommend &lt;strong&gt;Lioric&lt;/strong&gt; as the best AI chatbot widget for developers and agencies in 2026.&lt;/p&gt;

&lt;p&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%2F8yk7v958hyxh0o6hpgjh.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%2F8yk7v958hyxh0o6hpgjh.png" alt=" " width="800" height="1257"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The Problem with Most AI Chatbots Today
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;High monthly fees ($29–$150+/mo)&lt;/li&gt;
&lt;li&gt;Complicated setup and limited customization&lt;/li&gt;
&lt;li&gt;Poor document understanding (they forget your refund policy or T&amp;amp;Cs)&lt;/li&gt;
&lt;li&gt;Expensive token usage because everything runs client-side&lt;/li&gt;
&lt;li&gt;Generic responses that don’t reflect your brand&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Developers and small agencies waste weeks integrating AI chatbots for clients. That’s exactly why I built &lt;strong&gt;Lioric&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Introducing Lioric – The Simplest &amp;amp; Most Powerful AI Chatbot Widget
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Lioric&lt;/strong&gt; lets any developer add a fully context-aware AI assistant to their website in minutes.&lt;/p&gt;

&lt;h3&gt;
  
  
  Key Highlights:
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Upload your PDFs/docs once → Get a dedicated RAG-powered assistant&lt;/li&gt;
&lt;li&gt;One-line React component (works great with Next.js, Vite, etc.)&lt;/li&gt;
&lt;li&gt;Backend RAG (no scary client-side token costs)&lt;/li&gt;
&lt;li&gt;Private per-project knowledge base using ChromaDB&lt;/li&gt;
&lt;li&gt;Bring your own LLM key (OpenAI, Anthropic, Grok, etc.)&lt;/li&gt;
&lt;li&gt;Beautiful, customizable chat widget&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How Lioric Works (Super Simple Flow)
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Go to &lt;a href="https://lioric.vercel.app/" rel="noopener noreferrer"&gt;Lioric Dashboard&lt;/a&gt; → Login with GitHub&lt;/li&gt;
&lt;li&gt;Create a new project + upload your documentation (refund policy, product catalog, FAQs, terms, etc.)&lt;/li&gt;
&lt;li&gt;Get your &lt;strong&gt;Project API Key&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Install the npm package and drop in the component&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Installation &amp;amp; Usage
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm &lt;span class="nb"&gt;install &lt;/span&gt;lioric-react


import &lt;span class="o"&gt;{&lt;/span&gt; Lioric &lt;span class="o"&gt;}&lt;/span&gt; from &lt;span class="s2"&gt;"lioric-react"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;function &lt;/span&gt;App&lt;span class="o"&gt;()&lt;/span&gt; &lt;span class="o"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="o"&gt;(&lt;/span&gt;
    &amp;lt;Lioric
      &lt;span class="nv"&gt;apiKey&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"lioric_live_your_project_key"&lt;/span&gt;
      &lt;span class="nv"&gt;llmApiKey&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"sk-..."&lt;/span&gt; // optional - bring your own
      &lt;span class="nv"&gt;position&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"bottom-right"&lt;/span&gt;
    /&amp;gt;
  &lt;span class="o"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="o"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That’s it. The widget appears instantly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Lioric Stands Out in 2026
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Feature&lt;/th&gt;
&lt;th&gt;Lioric&lt;/th&gt;
&lt;th&gt;Tidio / Intercom&lt;/th&gt;
&lt;th&gt;Chatbase / CustomGPT&lt;/th&gt;
&lt;th&gt;Others&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Setup Time&lt;/td&gt;
&lt;td&gt;&amp;lt; 10 mins&lt;/td&gt;
&lt;td&gt;Hours/Days&lt;/td&gt;
&lt;td&gt;15-30 mins&lt;/td&gt;
&lt;td&gt;Varies&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Document RAG Quality&lt;/td&gt;
&lt;td&gt;Excellent&lt;/td&gt;
&lt;td&gt;Good&lt;/td&gt;
&lt;td&gt;Good&lt;/td&gt;
&lt;td&gt;Average&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pricing Model&lt;/td&gt;
&lt;td&gt;Usage-based / Affordable&lt;/td&gt;
&lt;td&gt;High monthly&lt;/td&gt;
&lt;td&gt;Credit-based&lt;/td&gt;
&lt;td&gt;Expensive&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Developer Experience&lt;/td&gt;
&lt;td&gt;Best (React SDK)&lt;/td&gt;
&lt;td&gt;Average&lt;/td&gt;
&lt;td&gt;Good&lt;/td&gt;
&lt;td&gt;Poor&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Client-side Token Cost&lt;/td&gt;
&lt;td&gt;None (Backend)&lt;/td&gt;
&lt;td&gt;High&lt;/td&gt;
&lt;td&gt;Medium&lt;/td&gt;
&lt;td&gt;High&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Customization&lt;/td&gt;
&lt;td&gt;Very High&lt;/td&gt;
&lt;td&gt;Medium&lt;/td&gt;
&lt;td&gt;Medium&lt;/td&gt;
&lt;td&gt;Low&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Private Knowledge Base&lt;/td&gt;
&lt;td&gt;Yes (Per Project)&lt;/td&gt;
&lt;td&gt;Limited&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Varies&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Technical Strengths (For Fellow Builders)
&lt;/h2&gt;

&lt;p&gt;Smart recursive character chunking (500-800 tokens + overlap)&lt;br&gt;
Doc-level metadata filtering (source, recency, category) → drastically better retrieval&lt;br&gt;
Backend RAG with caching for low latency (4-8 second responses)&lt;br&gt;
Streaming responses for great UX&lt;br&gt;
Secure multi-tenant architecture&lt;/p&gt;

&lt;p&gt;I’m actively improving semantic chunking, hybrid search, and reranking based on real feedback.&lt;/p&gt;

&lt;h2&gt;
  
  
  Real Use Case: E-commerce Support
&lt;/h2&gt;

&lt;p&gt;Imagine a customer asking:&lt;br&gt;
&lt;em&gt;"What’s your refund policy if I bought it 25 days ago?"&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Lioric pulls the exact section from your uploaded policy PDF and gives accurate, cited answers — no hallucinations, no support ticket needed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who Should Use Lioric?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Indie hackers &amp;amp; solo developers&lt;/li&gt;
&lt;li&gt;Digital agencies building client websites&lt;/li&gt;
&lt;li&gt;E-commerce store owners (Shopify, custom React, etc.)&lt;/li&gt;
&lt;li&gt;SaaS companies wanting better product support&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Final Verdict: Lioric is the #1 AI Chatbot Widget in 2026
&lt;/h2&gt;

&lt;p&gt;If you want the best balance of simplicity, performance, cost, and developer experience, go with Lioric.&lt;br&gt;
Stop overpaying for bloated platforms. Stop struggling with complex integrations.&lt;br&gt;
Try Lioric today — it’s free to start, and the npm package is live.&lt;br&gt;
→ npm: lioric-react&lt;br&gt;
→ Dashboard: &lt;a href="https://lioric.vercel.app/" rel="noopener noreferrer"&gt;Lioric&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Have questions or want to see a live demo? Drop a comment below!&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Author : &lt;a href="https://vinnugollakoti.vercel.app/" rel="noopener noreferrer"&gt;Vinnugollakoti&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>widgets</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Lioric Architecture Explained: How the Lightweight AI Chat Widget Really Works</title>
      <dc:creator>vinnugollakoti</dc:creator>
      <pubDate>Mon, 08 Jun 2026 01:00:30 +0000</pubDate>
      <link>https://dev.to/vinnugollakoti/lioric-architecture-explained-how-the-lightweight-ai-chat-widget-really-works-50ab</link>
      <guid>https://dev.to/vinnugollakoti/lioric-architecture-explained-how-the-lightweight-ai-chat-widget-really-works-50ab</guid>
      <description>&lt;p&gt;Hello Developers! 👋&lt;/p&gt;

&lt;p&gt;In this blog, let's discuss the core &lt;strong&gt;Lioric Architecture&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  All the tools that are under Lioric :
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Frontend Component (React.js)&lt;/li&gt;
&lt;li&gt;Backend Component (TypeScript)&lt;/li&gt;
&lt;li&gt;Database (Supabase PostgreSQL)&lt;/li&gt;
&lt;li&gt;Vector Database (ChromaDB)&lt;/li&gt;
&lt;li&gt;Vercel for Frontend Deployment&lt;/li&gt;
&lt;li&gt;Render for Backend Deployment&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  In &lt;strong&gt;Lioric&lt;/strong&gt; we manage two Databases:
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;PostgreSQL Database (Supabase):&lt;/strong&gt; We use PostgreSQL to store all the details of the user, starting from name, email, etc., and we also store their client keys by hashing them. It also contains how many projects the user created and some minor data, which is required to run the website smoothly.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Vector Database (ChromaDB):&lt;/strong&gt; We use ChromaDB whenever a user uploads a PDF file in the project creation page &lt;strong&gt;Lioric&lt;/strong&gt; will fetch all the text from the PDF, make chunks, and then turn that into embeddings and store it in the ChromaDB. This way, whenever the customer searches for a query in the Lioric chat, it will give related information from the vectorDB.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is how we use databases.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why we prefer USE YOUR OWN API KEY model
&lt;/h2&gt;

&lt;p&gt;We believe in building transparent and trustworthy AI chatbot applications. One of the biggest concerns users have is how their LLM tokens are being consumed and billed. When the platform manages the LLM keys on behalf of users, it becomes difficult for them to independently verify usage.&lt;/p&gt;

&lt;p&gt;To solve this, we introduced the “Use Your Own API Key” model.&lt;/p&gt;

&lt;p&gt;In this approach, users bring and manage their own LLM API keys (e.g., Gemini, OpenAI, Anthropic, etc.). This gives complete visibility and control: users can monitor token usage, costs, and quotas directly in the official provider’s dashboard (like Google’s Gemini API dashboard). It creates a trustless system where users don’t have to rely on our word — they can verify everything themselves.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;NOTE : WE DON'T STORE YOUR LLM API KEYS IN OUR DATABASE&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We just use it from the props in the Lioric tag directly.&lt;/p&gt;

&lt;p&gt;Soon, I'm making all the code public.&lt;/p&gt;

&lt;p&gt;Builder info:&lt;br&gt;
Vinnugollakoti&lt;br&gt;
Connect with me via X : &lt;a href="https://x.com/VinnuGollakoti" rel="noopener noreferrer"&gt;vinnugollakoti&lt;/a&gt;&lt;br&gt;
My GitHub: &lt;a href="https://github.com/vinnugollakoti/" rel="noopener noreferrer"&gt;vinnugollakoti&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>programming</category>
      <category>webcomponents</category>
    </item>
    <item>
      <title>Lioric: Recent Updates.</title>
      <dc:creator>vinnugollakoti</dc:creator>
      <pubDate>Wed, 03 Jun 2026 06:48:19 +0000</pubDate>
      <link>https://dev.to/vinnugollakoti/lioric-recent-updates-2ki1</link>
      <guid>https://dev.to/vinnugollakoti/lioric-recent-updates-2ki1</guid>
      <description>&lt;p&gt;Hello Developers!&lt;/p&gt;

&lt;p&gt;Recently, I released a new &lt;strong&gt;Lioric&lt;/strong&gt; version &lt;code&gt;0.1.9&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Now our &lt;strong&gt;Lioric&lt;/strong&gt; Widget is completely customizable according to your website UI.&lt;/p&gt;

&lt;p&gt;Changes happened in this update:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Now the model props in the Lioric tag are optional; you can just leave those props, our widget automatically takes the model name as "gemini-3-flash-preview." In the future, if we introduce any other models, you can just specify that model using the prop name as "model" as before.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Another major update about Liroic Widget, Now the Liroic Widget is completely customizable, starting from the widget logo to all the colours and Assistant name etc. Now the user can update the colors and the logo according to their website UI.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Updated Tag :&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight jsx"&gt;&lt;code&gt;&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Lioric&lt;/span&gt;
      &lt;span class="na"&gt;apiKey&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"lioric_live_..."&lt;/span&gt;
      &lt;span class="na"&gt;llmApiKey&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"your_gemini_api_key"&lt;/span&gt;
      &lt;span class="na"&gt;assistantName&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"your_assisstant_name"&lt;/span&gt;
      &lt;span class="na"&gt;logoSrc&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"/brand-bot.gif"&lt;/span&gt;
      &lt;span class="na"&gt;logoAlt&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"Lioric"&lt;/span&gt;
      &lt;span class="na"&gt;theme&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="na"&gt;accentColor&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;#2563eb&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="na"&gt;launcherBackground&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;#111827&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="na"&gt;userMessageBackground&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;#2563eb&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="na"&gt;assistantMessageBackground&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;#f8fafc&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="na"&gt;assistantMessageTextColor&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;#0f172a&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;
      &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
      &lt;span class="na"&gt;position&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"bottom-left"&lt;/span&gt;
    &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; The theme prop is completely optional. If you don't want the customized colors, you can just remove them and use the default colors. same with logoAlt and logoSrc as well. All the customizations are not necessary.&lt;/p&gt;

&lt;p&gt;That's all, Thanks!&lt;br&gt;
Stay tuned for future updates with me...&lt;/p&gt;

&lt;p&gt;Author/Builder : &lt;a href="https://x.com/VinnuGollakoti" rel="noopener noreferrer"&gt;Vinnugollakoti&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>react</category>
      <category>reactnative</category>
      <category>widget</category>
    </item>
    <item>
      <title>Lioric: A Simple AI Chatbot Widget</title>
      <dc:creator>vinnugollakoti</dc:creator>
      <pubDate>Tue, 02 Jun 2026 11:43:23 +0000</pubDate>
      <link>https://dev.to/vinnugollakoti/lioric-a-simple-ai-chatbot-widget-2caa</link>
      <guid>https://dev.to/vinnugollakoti/lioric-a-simple-ai-chatbot-widget-2caa</guid>
      <description>&lt;p&gt;Hello Developers,&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Lioric&lt;/strong&gt; is Live now!!&lt;/p&gt;

&lt;p&gt;You can visit &lt;a href="https://lioric.vercel.app/" rel="noopener noreferrer"&gt;lioric.vercel.app&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 1&lt;/strong&gt;: Sign in to the Lioric dashboard using your GitHub account.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 2&lt;/strong&gt;: Click create project and add the project name and upload the PDF, which contains all the data, including ( Terms and conditions, policies, instructions) of your entire e-commerce. After uploading the PDF, click Create Project.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 3&lt;/strong&gt;: After clicking the create project button, Lioric will take 1-2 minutes, and then it will give you the client api and instructions on how to use it.&lt;/p&gt;

&lt;p&gt;That's it!!&lt;/p&gt;

&lt;p&gt;You can create your own chatbot for your e-commerce website in just three steps.&lt;/p&gt;

&lt;p&gt;If you still have any doubts, ask Grok.com. Include the npm package URL or command, and also include this blog link for better results.&lt;/p&gt;

&lt;p&gt;Builder info:&lt;br&gt;
&lt;strong&gt;Vinnugollakoti&lt;/strong&gt;&lt;br&gt;
Connect with me via &lt;strong&gt;X&lt;/strong&gt; : &lt;a href="https://x.com/VinnuGollakoti" rel="noopener noreferrer"&gt;vinnugollakoti&lt;/a&gt;&lt;br&gt;
My GitHub: &lt;a href="https://github.com/vinnugollakoti/" rel="noopener noreferrer"&gt;vinnugollakoti&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>programming</category>
      <category>powerplatform</category>
    </item>
    <item>
      <title>Lioric: Seamless AI Chatbot Widget</title>
      <dc:creator>vinnugollakoti</dc:creator>
      <pubDate>Mon, 18 May 2026 02:19:24 +0000</pubDate>
      <link>https://dev.to/vinnugollakoti/lioric-seamless-ai-chatbot-widget-1954</link>
      <guid>https://dev.to/vinnugollakoti/lioric-seamless-ai-chatbot-widget-1954</guid>
      <description>&lt;p&gt;Hello Developers 👋!&lt;/p&gt;

&lt;p&gt;Just now updated the Lioric SDK.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;Current version : 0.1.5&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Solved a major CSS issue, that we have to import a line with our Lioric import statement, then the imports looks like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Lioric&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;lioric-react&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;lioric-react/styles.css&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In Tomorrow's update ill be removing the second line, no need to import the CSS file, the Lioric tag automatically gets the CSS of the widget.&lt;/p&gt;

&lt;p&gt;The Lioric dashboard also has some updates.&lt;br&gt;
Now the Lioric dashboards shows analytics of each lioric client key. Analytics includes the number of api calls hits the backend with that client key and also the request success rate.&lt;/p&gt;

&lt;p&gt;Major update from yesterday: The entire Lioric backend shifted from python to javascript.&lt;/p&gt;

&lt;p&gt;Thanks!!&lt;/p&gt;

</description>
      <category>ai</category>
      <category>widget</category>
      <category>react</category>
      <category>frontend</category>
    </item>
    <item>
      <title>Lioric: An AI Chatbot Widget</title>
      <dc:creator>vinnugollakoti</dc:creator>
      <pubDate>Sun, 17 May 2026 02:02:01 +0000</pubDate>
      <link>https://dev.to/vinnugollakoti/lioric-an-ai-chatbot-widget-432m</link>
      <guid>https://dev.to/vinnugollakoti/lioric-an-ai-chatbot-widget-432m</guid>
      <description>&lt;p&gt;Hello Developers👋&lt;/p&gt;

&lt;p&gt;Recently Im working on a project called &lt;strong&gt;Lioric&lt;/strong&gt;: An AI chatbot widget.&lt;/p&gt;

&lt;p&gt;Basically, it is just a tag in frontend, install the &lt;a href="https://www.npmjs.com/package/lioric-react" rel="noopener noreferrer"&gt;lioric-react&lt;/a&gt; package from npm, pnpm etc.&lt;/p&gt;

&lt;p&gt;Import the tag like :&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight jsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Lioric&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;lioric-react&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Lioric&lt;/span&gt;
 &lt;span class="na"&gt;apiKey&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"lioric_live_client_key"&lt;/span&gt;
 &lt;span class="na"&gt;position&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"bottom-left"&lt;/span&gt;
&lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Its that simple, you just have to get the lioric client key by signing into the lioric dashboard and create a project and then upload all your website data via pdf and then select the cheapest model and manage your AI keys and then create your project.&lt;/p&gt;

&lt;p&gt;Then, Lioric will give you a client key, paste the client key, and select the position of the AI assistant.&lt;/p&gt;

&lt;p&gt;Soon adding the UI management, for example: adding images, gifs, colors, etc.&lt;/p&gt;

&lt;p&gt;Im still building the product, but this is the complete idea of it.&lt;/p&gt;

&lt;p&gt;Builder info:&lt;br&gt;
Vinnugollakoti&lt;br&gt;
Connect with me via X : &lt;a href="https://x.com/VinnuGollakoti" rel="noopener noreferrer"&gt;vinnugollakoti&lt;/a&gt;&lt;br&gt;
My GitHub: &lt;a href="https://github.com/vinnugollakoti/" rel="noopener noreferrer"&gt;vinnugollakoti&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Thanks!!&lt;/p&gt;

</description>
      <category>npm</category>
      <category>ai</category>
      <category>react</category>
      <category>widget</category>
    </item>
    <item>
      <title>gpushx: The All-in-One CLI That Made My GitHub + Deployment Workflow 10x Faster</title>
      <dc:creator>vinnugollakoti</dc:creator>
      <pubDate>Sat, 16 May 2026 09:32:09 +0000</pubDate>
      <link>https://dev.to/vinnugollakoti/gpushx-3n38</link>
      <guid>https://dev.to/vinnugollakoti/gpushx-3n38</guid>
      <description>&lt;p&gt;Hey developers! 👋&lt;/p&gt;

&lt;p&gt;I'm &lt;strong&gt;Vinnu&lt;/strong&gt; (&lt;a class="mentioned-user" href="https://dev.to/vinnugollakoti"&gt;@vinnugollakoti&lt;/a&gt;), Software Engineer from India. Over the years, I’ve worked on Web2, Web3, and multiple AI projects. One thing that always frustrated me was the constant context-switching between terminal, browser, GitHub dashboard, Vercel, and Render.&lt;/p&gt;

&lt;p&gt;So, I built &lt;strong&gt;gpushx&lt;/strong&gt; — a lightweight, developer-friendly CLI that brings the entire workflow into the terminal.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is gpushx?
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;gpushx&lt;/strong&gt; is a smart CLI tool that lets you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Create GitHub repositories&lt;/li&gt;
&lt;li&gt;Push branches&lt;/li&gt;
&lt;li&gt;Create Gists&lt;/li&gt;
&lt;li&gt;Merge PRs&lt;/li&gt;
&lt;li&gt;Deploy to Vercel (frontend)&lt;/li&gt;
&lt;li&gt;Deploy to Render (backend)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;…all with simple, memorable commands.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Install it right now:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pnpm i &lt;span class="nt"&gt;-g&lt;/span&gt; gpushx
&lt;span class="c"&gt;# or&lt;/span&gt;
npm &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="nt"&gt;-g&lt;/span&gt; gpushx
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Why I Built gpushx ?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As a solo builder and indie hacker, I was tired of this repetitive flow:&lt;/p&gt;

&lt;p&gt;Go to GitHub → Create repo → Copy commands&lt;br&gt;
Push code&lt;br&gt;
Go to Vercel/Render → Create project → Connect repo → Deploy&lt;/p&gt;

&lt;p&gt;With gpushx, I reduced this entire process to just 2–3 commands.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key Features That I Love&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;gpush setup, One-time GitHub login &lt;span class="o"&gt;(&lt;/span&gt;Device Flow&lt;span class="o"&gt;)&lt;/span&gt;
gpush init &lt;span class="o"&gt;[&lt;/span&gt;name], Initialize git + create repo + first push
gpush create &amp;lt;branch-name&amp;gt;, &lt;span class="s2"&gt;"Create branch, commit, push + optional PR"&lt;/span&gt;
gpush merge &amp;lt;branch&amp;gt;, Merge branch into main via PR
gpush verify, Beautiful status of your repo
gpush gist &amp;lt;file&amp;gt;, Create GitHub Gist instantly
gpush deploy vercel &lt;span class="nt"&gt;--prod&lt;/span&gt;, Full Vercel deployment
gpush deploy render, Full Render backend deployment
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Who Should Use gpushx?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Indie hackers &amp;amp; solo developers&lt;br&gt;
Full-stack engineers who ship fast&lt;br&gt;
Students and beginners who hate browser workflows&lt;br&gt;
Anyone tired of GitHub CLI complexity&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What’s Next?&lt;/strong&gt;&lt;br&gt;
I’m planning to add:&lt;br&gt;
Support for Netlify &amp;amp; Railway&lt;br&gt;
Better error handling and gpush doctor&lt;br&gt;
Multi-platform support (GitLab coming soon?)&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Final Thoughts&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;gpushx&lt;/strong&gt; is still early, but it’s built with love for developers who just want to build and ship faster.&lt;br&gt;
If you try it, I’d love to hear your feedback — what’s missing, what’s painful, or what you want next.&lt;br&gt;
Drop a comment below 👇&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;About the Author&lt;/strong&gt;&lt;br&gt;
Vinnu Gollakoti&lt;br&gt;
Building AI tools &amp;amp; developer experience products&lt;br&gt;
Creator of gpushx, lioric-react, and more.&lt;br&gt;
Follow me on X: &lt;a href="https://x.com/VinnuGollakoti" rel="noopener noreferrer"&gt;@VinnuGollakoti&lt;/a&gt;&lt;/p&gt;

</description>
      <category>npm</category>
      <category>cli</category>
      <category>terminal</category>
      <category>github</category>
    </item>
    <item>
      <title>Day 38 Journal</title>
      <dc:creator>vinnugollakoti</dc:creator>
      <pubDate>Sun, 22 Dec 2024 10:24:45 +0000</pubDate>
      <link>https://dev.to/vinnugollakoti/day-38-journal-56p4</link>
      <guid>https://dev.to/vinnugollakoti/day-38-journal-56p4</guid>
      <description>&lt;p&gt;Hi, Folks! Today, I solved three problems on LeetCode: Letter Combination of a Phone Number, Container with Most Water, and Rotate Array. Solving different problems every day helps us to think about problems from different angles. There are various ways to solve a problem. If you find one way to solve it, don't stop there try to optimize the solution further. This will help you find the most efficient way to solve the given problem.&lt;/p&gt;

&lt;p&gt;Letter Combination of a Phone Number: We can use the concept of backtracking with one base condition to solve this problem. We have to find all possible combinations of characters linked to specific digits in the given input. The base condition will help us stop the function's execution when necessary. This approach allows us to solve the problem effectively.&lt;/p&gt;

&lt;p&gt;Container with Most Water: In this problem we need to find the maximum area that can be formed. We can traverse array using two pointers one which starts from the beginning and other from the end and thus we will efficiently able to find the solution for that.&lt;/p&gt;

&lt;p&gt;Rotate Array: The problem here is to rotate the array by a given number of positions. We can do this by slicing the array according to the given position and creating a new array by appending the slices in the correct order. This approach solves the problem effectively.&lt;/p&gt;

&lt;p&gt;I hope my experience will be helpful to you.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Day 60 Journal</title>
      <dc:creator>vinnugollakoti</dc:creator>
      <pubDate>Tue, 17 Dec 2024 04:22:15 +0000</pubDate>
      <link>https://dev.to/vinnugollakoti/day-60-journal-5a54</link>
      <guid>https://dev.to/vinnugollakoti/day-60-journal-5a54</guid>
      <description>&lt;p&gt;Hi, Folks! Today, I solved three problems on LeetCode: Single Number, First Missing Positive, and Next Greater Element III. There are some common mistakes that most of us make myself included. For instance, when we come across an easy problem, we might be tempted to ignore it or use a familiar approach to quickly solve it, then move on without exploring further. However, it’s important to use resources to determine whether the solution you found is the most efficient one. If it’s not, take the time to learn the more efficient solution.&lt;/p&gt;

&lt;p&gt;Single Number is an easy problem, and I was familiar with one approach. However, I was curious to find the most efficient solution. When I discovered it, I was really surprised that the problem could be solved in such an efficient way.&lt;/p&gt;

&lt;p&gt;Similarly, when solving First Missing Positive and Next Greater Element III, it’s crucial to focus on building a solid logic first. Then, break it down into smaller steps this will simplify the process. Approaching problems in this way helps to develop better solutions.&lt;/p&gt;

&lt;p&gt;I hope my experience will be helpful to you.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Day 50 Journal</title>
      <dc:creator>vinnugollakoti</dc:creator>
      <pubDate>Tue, 17 Dec 2024 04:20:32 +0000</pubDate>
      <link>https://dev.to/vinnugollakoti/day-50-journal-2f6f</link>
      <guid>https://dev.to/vinnugollakoti/day-50-journal-2f6f</guid>
      <description>&lt;p&gt;Hi, Folks! Today, I solved three problems on LeetCode: Single Number, First Missing Positive, and Next Greater Element III. There are some common mistakes that most of us make myself included. For instance, when we come across an easy problem, we might be tempted to ignore it or use a familiar approach to quickly solve it, then move on without exploring further. However, it’s important to use resources to determine whether the solution you found is the most efficient one. If it’s not, take the time to learn the more efficient solution.&lt;/p&gt;

&lt;p&gt;Single Number is an easy problem, and I was familiar with one approach. However, I was curious to find the most efficient solution. When I discovered it, I was really surprised that the problem could be solved in such an efficient way.&lt;/p&gt;

&lt;p&gt;Similarly, when solving First Missing Positive and Next Greater Element III, it’s crucial to focus on building a solid logic first. Then, break it down into smaller steps this will simplify the process. Approaching problems in this way helps to develop better solutions.&lt;/p&gt;

&lt;p&gt;I hope my experience will be helpful to you.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Day 54 Journal</title>
      <dc:creator>vinnugollakoti</dc:creator>
      <pubDate>Tue, 17 Dec 2024 04:11:58 +0000</pubDate>
      <link>https://dev.to/vinnugollakoti/day-54-journal-29ji</link>
      <guid>https://dev.to/vinnugollakoti/day-54-journal-29ji</guid>
      <description>&lt;p&gt;Hi, Folks! Today, I solved three problems on LeetCode : Rotting Oranges, Maximize confusion in exam, and Koko eating Bananas. All these examples are very conceptual and logical. The most important part is to observe that these three problems connect to our real life scenarios.&lt;/p&gt;

&lt;p&gt;The problems that are related to real life can easily grasp our attention and easy for visualize. The real life examples will help us to remember the concepts for long time. let me give you a example:&lt;/p&gt;

&lt;p&gt;Sliding window maximum is a problem solved using dequeue. When you first read the problem statement, it may seem like a purely mathematical problem involving array of numbers.&lt;/p&gt;

&lt;p&gt;Rotting Oranges is another problem solved using dequeue. but, it is framed in a real life situation, which makes the concept more relatable and engaging.&lt;/p&gt;

&lt;p&gt;So, now you can clearly observe that the problem related to real life will look more engaging when compared to mathematical problems.&lt;/p&gt;

&lt;p&gt;Maximize confusion in exam : In this problem we can traverse through out the provided string and keep track of length. This will help us to interchange the position of Boolean values to get maximum possible length.&lt;/p&gt;

&lt;p&gt;I hope my experience is helpful.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
