<?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: zvspany</title>
    <description>The latest articles on DEV Community by zvspany (@zvspany).</description>
    <link>https://dev.to/zvspany</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%2F3817194%2F53ef80e9-6c8e-4605-a41c-d6d954315d1d.png</url>
      <title>DEV Community: zvspany</title>
      <link>https://dev.to/zvspany</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zvspany"/>
    <language>en</language>
    <item>
      <title>Building an open-source crypto and fiat converter with Next.js 14</title>
      <dc:creator>zvspany</dc:creator>
      <pubDate>Tue, 10 Mar 2026 15:44:11 +0000</pubDate>
      <link>https://dev.to/zvspany/building-an-open-source-crypto-and-fiat-converter-with-nextjs-14-3faf</link>
      <guid>https://dev.to/zvspany/building-an-open-source-crypto-and-fiat-converter-with-nextjs-14-3faf</guid>
      <description>&lt;p&gt;I recently built a small open-source project called &lt;strong&gt;NexCurrency&lt;/strong&gt; – a fiat and crypto converter built with Next.js 14, TypeScript, Tailwind CSS, and shadcn-style UI components.&lt;/p&gt;

&lt;p&gt;The goal was to create a clean system that can convert between:&lt;/p&gt;

&lt;p&gt;• fiat → fiat&lt;br&gt;
• fiat → crypto&lt;br&gt;
• crypto → fiat&lt;br&gt;
• crypto → crypto&lt;/p&gt;

&lt;p&gt;The tricky part was combining fiat and crypto APIs. Fiat APIs usually return pair-based exchange rates, while crypto APIs return USD prices per asset.&lt;/p&gt;

&lt;p&gt;To simplify this, the app normalizes both into a shared internal model using a &lt;code&gt;usdPrice&lt;/code&gt; value. Conversions then become:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;amount * (from.usdPrice / to.usdPrice)&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;This approach avoids needing direct pairs for every asset combination and keeps the system provider-agnostic.&lt;/p&gt;

&lt;p&gt;Tech stack:&lt;br&gt;
• Next.js 14 (App Router)&lt;br&gt;
• TypeScript&lt;br&gt;
• Tailwind CSS&lt;br&gt;
• Zod validation&lt;br&gt;
• CoinGecko API (crypto prices)&lt;br&gt;
• Frankfurter API (fiat rates)&lt;/p&gt;

&lt;p&gt;GitHub repository:&lt;br&gt;
&lt;a href="https://github.com/zvspany/NexCurrency" rel="noopener noreferrer"&gt;https://github.com/zvspany/NexCurrency&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I'd really appreciate any feedback on the architecture, UI/UX, or overall project structure.&lt;/p&gt;

</description>
      <category>nextjs</category>
      <category>opensource</category>
      <category>webdev</category>
      <category>react</category>
    </item>
  </channel>
</rss>
