<?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: Rodrigo Veiga</title>
    <description>The latest articles on DEV Community by Rodrigo Veiga (@rodriveiga01).</description>
    <link>https://dev.to/rodriveiga01</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%2F1987969%2F36ade9e6-8c4c-4444-b4d4-21746054ac4f.png</url>
      <title>DEV Community: Rodrigo Veiga</title>
      <link>https://dev.to/rodriveiga01</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rodriveiga01"/>
    <language>en</language>
    <item>
      <title>Micro-Commits: Why You Should Do 'Em</title>
      <dc:creator>Rodrigo Veiga</dc:creator>
      <pubDate>Thu, 02 Jan 2025 22:02:48 +0000</pubDate>
      <link>https://dev.to/rodriveiga01/micro-commits-why-you-should-do-em-imp</link>
      <guid>https://dev.to/rodriveiga01/micro-commits-why-you-should-do-em-imp</guid>
      <description>&lt;h1&gt;
  
  
  What's a Micro-Commit?
&lt;/h1&gt;

&lt;p&gt;Instead of slamming all your changes into one big commit, break 'em down into tiny ones. So, instead of one massive "I changed everything!" commit, you might do three smaller ones.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Bother?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Keeps Things Clean:&lt;/strong&gt; Easier to see what changed when and where. &lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Less Stress:&lt;/strong&gt; No more sweating over pushing a huge update. Small steps mean small risks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Team Love:&lt;/strong&gt; Helps your team follow your changes without needing a treasure map.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How to Start:
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Don't Change Much:&lt;/strong&gt; Just commit more often. Like, if you're tweaking functions for a new library, do:

&lt;ul&gt;
&lt;li&gt;"Processing functions now use new lib"&lt;/li&gt;
&lt;li&gt;"Calculations updated for new lib"&lt;/li&gt;
&lt;li&gt;"Logging with new library setup"&lt;/li&gt;
&lt;/ul&gt;


&lt;/li&gt;

&lt;li&gt;

&lt;strong&gt;Clear Messages:&lt;/strong&gt; Tell what and why in your commit messages. It's like leaving breadcrumbs for your future self or your team.&lt;/li&gt;

&lt;/ul&gt;

&lt;h2&gt;
  
  
  Tools to Help:
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Git:&lt;/strong&gt; It's built for this. Commit away!&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;GitLens:&lt;/strong&gt; Or similar tools in VSCode show your commits nicely. Even without it, git's basic stuff works.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try It Out:
&lt;/h2&gt;

&lt;p&gt;Challenge yourself for a week. See if it feels less like a chore and more like a breeze.&lt;/p&gt;

&lt;h2&gt;
  
  
  Wrap Up:
&lt;/h2&gt;

&lt;p&gt;Micro-commits might seem like more work, but they make your life easier in the long run. Less headache, more control. Give it a shot, and let's talk about it in the comments!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Challenge:&lt;/strong&gt; Go for it this week, then share how it went!&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Why simple and easy apps are not a future but a choice</title>
      <dc:creator>Rodrigo Veiga</dc:creator>
      <pubDate>Thu, 29 Aug 2024 22:51:33 +0000</pubDate>
      <link>https://dev.to/rodriveiga01/why-simple-and-easy-apps-are-not-a-future-but-a-choice-12gg</link>
      <guid>https://dev.to/rodriveiga01/why-simple-and-easy-apps-are-not-a-future-but-a-choice-12gg</guid>
      <description>&lt;p&gt;So your thinking... Shouldn't the future be simple and easy apps because people as time goes want to do less and produce more. &lt;/p&gt;

&lt;p&gt;I will respond in a way that will change your point of view in the situation. It's going to be a long article, if you don't want to read go to the bullet points section at the end 👍&lt;/p&gt;

&lt;h2&gt;
  
  
  A trip to the past
&lt;/h2&gt;

&lt;p&gt;It's 2007 and the world is watching Steve Jobs introducing the first ever smartphone "The iPhone". When it is announced we are introduced to mobile apps, applications conceived to small devices with a 9:16 ratio that work by touch&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6nswd8qwnh2pojxpccgq.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6nswd8qwnh2pojxpccgq.png" alt="Steve Jobs in front of a screen saying iPhone" width="800" height="639"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The first apps are designed with an UI that mimics the real world with a REALLY complicated name "Skeuomorphism". This was the default option in the time because it made people familiar with the buttons and shapes because they were similar to the everyday life objects&lt;/p&gt;

&lt;p&gt;Then the company's start changing the design because there's always room to innovate so they come up with flat design. Flat design doesn't mimic the real world but makes everything easier to draw and simple to see&lt;/p&gt;

&lt;p&gt;For example let's say you are designing a calculator app logo, you have two options:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The option of "Skeuomorphism design" (the left one)&lt;/li&gt;
&lt;li&gt;The option of "Flat design" (the right one)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F5sjjmzbr5b581zmq322y.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F5sjjmzbr5b581zmq322y.png" alt="Calculator with different design choices" width="602" height="299"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Maybe you chose flat or maybe you chose skeuomorphism but that's not the thing in discussion, the thing is that we can all agree that the first option seems outdated. Why is that? Well obvious, it was introduced first and then replaced.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why are we talking about the mobile app UI history?
&lt;/h2&gt;

&lt;p&gt;This introduction was to show that the landscape always evolves, for better or for worse it always evolves.&lt;/p&gt;

&lt;p&gt;The UI is a thing that matters a lot in an app and the way the industry is moving is hinting to a new shift...&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;The AI User Interface&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;AI is a thing that's coming to stay. Whether you like it or not it's true.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F4mscyt90k56d0wefnoxr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F4mscyt90k56d0wefnoxr.png" alt="Robot looking at camera" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;As the AI evolves it starts to do a lot of things maybe even too much. This means that some apps in the future could be just a text box or a text voice input and it does the thing for you.&lt;/p&gt;

&lt;p&gt;This idea is not made by me... Apple it self is encouraging developers to implement a new feature in their IOS apps called&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fulqo60odqhvhbqcxtk2j.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fulqo60odqhvhbqcxtk2j.png" alt="App intents logo" width="774" height="592"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;And now you're going to say: "App intents just allows Siri to do actions of the app but the apps still have UI"&lt;/p&gt;

&lt;p&gt;And that's correct but I don't doubt that maybe just MAYBE we could see a future that an app is just a App intent and you just say Siri to do a thing and it does the action of the app&lt;/p&gt;

&lt;p&gt;Of course this is speculation but it could happen 🤷&lt;/p&gt;

&lt;h2&gt;
  
  
  The main point
&lt;/h2&gt;

&lt;p&gt;So are simple apps the future? Yes and No&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F0541z3so9rxzik62j4xz.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F0541z3so9rxzik62j4xz.png" alt="Keep it simple sign" width="800" height="651"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If a simple app is just an AI doing an action, me personally I don't like that future&lt;/p&gt;

&lt;p&gt;If a simple app is an app with simple UI and simple UX that the user does the essential and it gets the job done, I don't see it in a bad way but there's some flaws:&lt;/p&gt;

&lt;p&gt;If you want the user to do the bare minimum or the essential the app becomes less exciting because there's just one thing or two to do and it does the rest. But why is this a bad thing?&lt;/p&gt;

&lt;p&gt;Me as a user of a website or app I want to use it, experiment and maybe try new things in the app. I like to have settings and experiment but not too much. Just the essential...&lt;/p&gt;

&lt;p&gt;So this comes to a conclusion of three ways:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Or you have a SIMPLE app that is an AI doing an action and nothing else&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Or you have a simple app that has the essential features and settings to keep the user excited to use the app. They may or may not have AI to assist but isn't the main way to interact&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Or you have a complex app with a lot of features and settings that keeps the user excited but can be a little overwhelming without the right tutorial&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What is the right way? It's in the title "A Choice" &lt;/p&gt;

&lt;h2&gt;
  
  
  Bullet points ⏱️
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;App design has evolved from skeuomorphism to flat design&lt;/li&gt;
&lt;li&gt;AI User Interfaces may represent the next major shift in app design&lt;/li&gt;
&lt;li&gt;Apple's App Intents feature hints at a potential future of voice-controlled apps&lt;/li&gt;
&lt;li&gt;The article presents three potential futures for app design:

&lt;ul&gt;
&lt;li&gt;AI-driven apps with minimal UI&lt;/li&gt;
&lt;li&gt;Simple apps with essential features that may or may not have an AI assist&lt;/li&gt;
&lt;li&gt;Complex apps with numerous features&lt;/li&gt;
&lt;/ul&gt;


&lt;/li&gt;

&lt;li&gt;The "right" approach depends on user preferences and specific use cases&lt;/li&gt;

&lt;li&gt;The future of app design involves balancing simplicity, functionality, and user engagement&lt;/li&gt;

&lt;li&gt;AI integration in apps raises questions about the role of traditional UI elements&lt;/li&gt;

&lt;li&gt;The evolution of app design impacts both users and developers&lt;/li&gt;

&lt;/ul&gt;

&lt;h2&gt;
  
  
  Ignore
&lt;/h2&gt;

&lt;p&gt;I'm the developer of the app "QuickCoords". It combines simplicity with accuracy and presents a simple way to calculate and navigate to coordinates. See more in: &lt;a href="https://rodriveiga01.github.io/quickCoords_website/" rel="noopener noreferrer"&gt;https://rodriveiga01.github.io/quickCoords_website/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Thank you for reading the article 😁&lt;/p&gt;

</description>
      <category>ui</category>
      <category>ux</category>
      <category>design</category>
    </item>
    <item>
      <title>How to update your favicon on your website</title>
      <dc:creator>Rodrigo Veiga</dc:creator>
      <pubDate>Tue, 27 Aug 2024 16:51:03 +0000</pubDate>
      <link>https://dev.to/rodriveiga01/how-to-update-your-favicon-on-your-website-4k1a</link>
      <guid>https://dev.to/rodriveiga01/how-to-update-your-favicon-on-your-website-4k1a</guid>
      <description>&lt;p&gt;Hello I'm Rodrigo Veiga and I'm the developer of the app QuickCoords (an app of compass exploration and calculation of coordinates).&lt;/p&gt;

&lt;h2&gt;
  
  
  What's a favicon
&lt;/h2&gt;

&lt;p&gt;A favicon (short for favorite icon) is a file containing one or more small icons associated with a particular website (&lt;a href="https://en.wikipedia.org/wiki/Favicon" rel="noopener noreferrer"&gt;Source&lt;/a&gt;)&lt;/p&gt;

&lt;p&gt;In simple terms a favicon is the little top icon before your website domain that represents normally the logo of the website. Here's an example of the favicon of Wikipedia:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.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%2Fdri421xnnetxjw175xiz.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.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%2Fdri421xnnetxjw175xiz.png" alt="Image of the favicon of wikipedia website"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How to change the favicon of my website?
&lt;/h2&gt;

&lt;p&gt;If you're like me you're struggling to do such a simple thing as changing a favicon. Don't worry I have a complete solution for you 🙃!&lt;/p&gt;

&lt;h3&gt;
  
  
  🚫 Favicon.ico 🚫
&lt;/h3&gt;

&lt;p&gt;A simple solution seems to create a favicon.ico file and just use it but unfortunately it's not that simple&lt;/p&gt;

&lt;p&gt;For example, if you see your website in an Apple device you would not see any favicon... Why? Because Apple requires an additional configuration called "apple-touch-icon"&lt;/p&gt;

&lt;p&gt;For Safari you need a SVG file because of some MacBooks Touch Bar and pinned websites&lt;/p&gt;

&lt;h3&gt;
  
  
  How to do it?
&lt;/h3&gt;

&lt;p&gt;So let's get to work 🔨:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You could generate all by yourself but I don't recommend because you could get errors. What I recommend is using this &lt;a href="https://realfavicongenerator.net" rel="noopener noreferrer"&gt;website&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media.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%2F9zgqdym39fktd5wrswg0.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.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%2F9zgqdym39fktd5wrswg0.png" alt="Supported platforms of the website"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;As you see the website supports the most famous platforms and browsers&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;After you upload your logo the website will give you options for each platform and browser. It's not bad keeping all by default but you should pay attention to detail 😉&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Then just download the pack of the files and put in the public folder or other folder on your website directory&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media.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%2Fln2oyz6ec4xr5bzlvi3d.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.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%2Fln2oyz6ec4xr5bzlvi3d.png" alt="Files in public folder"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;And finally you just insert the code in your index.html. Normally it should look like this or similar:&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media.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%2Fk565nx6k2bfm8ludcja3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.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%2Fk565nx6k2bfm8ludcja3.png" alt="Code"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How to clear caches of favicon in Safari
&lt;/h2&gt;

&lt;p&gt;Safari has a cache of Safari and when developing the website in localhost it sometimes show the previous non favicon because its in cache.&lt;/p&gt;

&lt;p&gt;To clear it:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Quit Safari. Select safari and do CMD + Q&lt;/li&gt;
&lt;li&gt;Using Finder, click &lt;strong&gt;Go&lt;/strong&gt; then &lt;strong&gt;Go to Folder&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Enter &lt;strong&gt;~/Library/Safari/Favicon Cache/&lt;/strong&gt; in the window that pops up and go to this location&lt;/li&gt;
&lt;li&gt;Select all the items and delete them. Also clear your bin&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Done!
&lt;/h2&gt;

&lt;p&gt;If you've done all this and its not working restart your browser or clear caches.&lt;/p&gt;

&lt;p&gt;Now your done, you now have your new favicon 🎉&lt;/p&gt;

&lt;p&gt;If you have any more questions please let me know in the comments 😁&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>beginners</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
