<?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: Aptex - we create software</title>
    <description>The latest articles on DEV Community by Aptex - we create software (@aptex).</description>
    <link>https://dev.to/aptex</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%2F746109%2Ffb688ab8-11cc-4061-9411-4fef7c1df709.jpg</url>
      <title>DEV Community: Aptex - we create software</title>
      <link>https://dev.to/aptex</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/aptex"/>
    <language>en</language>
    <item>
      <title>Top 8 Website Mistakes</title>
      <dc:creator>Aptex - we create software</dc:creator>
      <pubDate>Thu, 16 Dec 2021 19:41:18 +0000</pubDate>
      <link>https://dev.to/aptex/top-8-website-mistakes-1d8b</link>
      <guid>https://dev.to/aptex/top-8-website-mistakes-1d8b</guid>
      <description>&lt;p&gt;When creating a website you should definitely avoid these 8 common mistakes - it's easier than you think!&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Your website is not responsive
&lt;/h3&gt;

&lt;p&gt;We're almost in the year 2022 and still there are plenty of websites out there that aren't mobile friendly - or responsive.&lt;br&gt;
This isn't only a big issue when it comes to your users, because the majority of people browse the web on their phones, but it also affects your websites SEO, as Google started ranking Websites that aren't optimised for mobile devices lower years ago.&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%2Fdrh36panzcoc0sed4449.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%2Fdrh36panzcoc0sed4449.png" alt="Desktop vs Mobile vs Tablet Market Share Worldwide&amp;lt;br&amp;gt;
Jan 2018 - Dec 2021"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  2. Your website has bad usability
&lt;/h3&gt;

&lt;p&gt;The most beautifully designed website with highly optimised SEO content is worthless if it isn't usable. It's not that difficult to provide a decent user experience with following a few simple best practices. For example it is important for mobile users to put the navigation in an easily reachable place. Therefore you could simply use a bottom bar navigation (see image below) instead of a hamburger menu. Or at least put the hamburger menu button on the top right, because the majority of people uses their phone with the right hand.&lt;/p&gt;

&lt;p&gt;We're using a bottom bar in our &lt;a href="https://aptex.gumroad.com/l/portfolio-template-01" rel="noopener noreferrer"&gt;free portfolio template for developers&lt;/a&gt;.&lt;br&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%2Fs2jemfcz5f705sdiudgc.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%2Fs2jemfcz5f705sdiudgc.png" alt="Website with a bottom bar navigation"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;
  
  
  3. You don't use image descriptions
&lt;/h3&gt;

&lt;p&gt;An often neglected aspect of web development besides usability is accessibility. A small step in the right direction to more accessibility is providing clear and expressive image descriptions. It's not enough to just put the text below the image, but provide a functional description in the image's alt-attribute.&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%2Fan47cfyk03los0iy1kok.jpg" 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%2Fan47cfyk03los0iy1kok.jpg" alt="A light brown dog running happily through water - probably the sea or a lake - with its tongue out"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;An alt description for the above image could looks something like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;img&lt;/span&gt; &lt;span class="na"&gt;src=&lt;/span&gt;&lt;span class="s"&gt;"./dog.jpg"&lt;/span&gt; &lt;span class="na"&gt;alt=&lt;/span&gt;&lt;span class="s"&gt;"A light brown dog running happily through water - probably the sea or a lake - with its tongue out"&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Besides the positive effects on accessibility this also has an impact on your SEO.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. You don't provide a clear call to action
&lt;/h3&gt;

&lt;p&gt;A call to action is essentially the one thing you want your user to do. It could be numerous things, like asking the user to make a phone call, sending an email, submitting a contact form or ordering something. It's one of the most important things for lead generation and sales on the internet.&lt;/p&gt;

&lt;p&gt;When designing a "Call To Action" you make use of the user's habits like reading from left to right (or right to left, in languages where that's the standard) or purposefully directing the user to the buttons they should click by making use of various design elements.&lt;/p&gt;

&lt;p&gt;It's crucial, that the user can reach the desired goal with as little friction as possible.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. You are missing out on analytics
&lt;/h3&gt;

&lt;p&gt;As the legendary engineer W. Edwards Deming put it&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Without data, you're just another person with an opinion.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Who are my users, where do they come from, which devices and browsers do they use and how many of them are actually converting? Getting all of these information about your website visitors is actually pretty simple and extremely insightful.&lt;/p&gt;

&lt;p&gt;There are plenty of solutions out there, that can help you to learn more about your users. Obviously there are big players like Google Analytics or Matomo, but there's also enough small indie competition, like for example &lt;a href="https://plausible.io" rel="noopener noreferrer"&gt;plausible.io&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;With all the knowledge you gain through the analytics, you can then create better tailormade experiences for your users.&lt;/p&gt;

&lt;p&gt;It's often very easy so find out why your conversion rate isn't as high as you want it to be.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Your copy sucks
&lt;/h3&gt;

&lt;p&gt;On the one hand it's important to write copy that will cater to the search engines, so your site will actually be found. A good rule of thumb for headings is using questions, that a potential visitor of your site would ask themselves and then proceed to enter the exact phrase into google.&lt;/p&gt;

&lt;p&gt;But on the other hand you also should not stuff your website copy with keywords and actually provide value to your users in a clear and concise way.&lt;br&gt;
By following these simple tips you immediately have a positive impact on your website's SEO&lt;/p&gt;

&lt;h3&gt;
  
  
  7. Your page is slow
&lt;/h3&gt;

&lt;p&gt;Speed is key - When your site is slow or doesn't respond quickly on user interactions, people tend to get frustrated easily and leave your site.&lt;br&gt;
Get rid of unused JavaScript and CSS, minify your files, optimize images for size and leverage the power of a CDN.&lt;br&gt;
Also your hosting environment plays an important role in pagespeed as well!&lt;/p&gt;

&lt;p&gt;We'll soon publish an in-depth article about ways to optimize your pagespeed.&lt;/p&gt;

&lt;h3&gt;
  
  
  8. You are using outdated software
&lt;/h3&gt;

&lt;p&gt;When using widely used software, such as WordPress, Typo3, Shopware, etc. there is a huge risk to become the victim of hackers. They make use of exploits and other commonly known security breaches. Thus it's important to keep the software you use up to date.&lt;br&gt;
But it's not just done with the software itself. If you use a CMS you are probably using themes and plugins and they are a risk nonetheless.&lt;br&gt;
If you built your site from scratch you should also keep an eye on the dependecies you have in your project.&lt;/p&gt;

&lt;h3&gt;
  
  
  Conclusion
&lt;/h3&gt;

&lt;p&gt;These are some of the most common mistakes we encounter on a lot of websites and a few suggestions on how to fix them.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>html</category>
      <category>beginners</category>
      <category>seo</category>
    </item>
    <item>
      <title>What I've learned from the first free product I've created</title>
      <dc:creator>Aptex - we create software</dc:creator>
      <pubDate>Mon, 08 Nov 2021 08:30:39 +0000</pubDate>
      <link>https://dev.to/aptex/what-ive-learned-from-the-first-free-product-ive-created-2cka</link>
      <guid>https://dev.to/aptex/what-ive-learned-from-the-first-free-product-ive-created-2cka</guid>
      <description>&lt;p&gt;Since the beginning of the year I've spent an excessive amount of time on tech twitter, slowly and steadily building an audience.&lt;/p&gt;

&lt;p&gt;As a means to give back to the community and in order to build myself a portfolio of free products (which I also plan on expanding to paid products later on) I recently created a &lt;a href="https://aptex.gumroad.com/l/portfolio-template-01"&gt;free portfolio template&lt;/a&gt;, mainly targeted to (beginner) developers.&lt;/p&gt;

&lt;p&gt;From the beginning I knew, I wanted to create a portfolio template as my first product, because I come across of novice developers who are trying to build their portfolio. Often times (frontend) developers can be exceptional problem solvers and write decent code even as juniors, but struggle a lot with (UI) design.&lt;/p&gt;

&lt;p&gt;Since this is something that I consider myself pretty well-versed in, I decided to offer this template to help them showcase their work in a way, that's not only pleasant to look at, but is also accessible at least to some degree.&lt;/p&gt;

&lt;p&gt;I'm in no way an accessibility expert, but I try to apply the knowledge I have to all products I design.The least I can do is aiming for WCAG AA color contrast standards.&lt;/p&gt;

&lt;h2&gt;
  
  
  Ask audience first
&lt;/h2&gt;

&lt;p&gt;So the first thing I did, was to ask people on twitter, what kind of content they'd expect to find in a developer's portfolio.&lt;/p&gt;

&lt;p&gt;The takeaway was, that I portfolio should include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Who you are&lt;/li&gt;
&lt;li&gt;What you do&lt;/li&gt;
&lt;li&gt;Examples of your work&lt;/li&gt;
&lt;li&gt;How to get in contact&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Also it should be simple to navigate and easily accessible from any device.&lt;/p&gt;

&lt;h2&gt;
  
  
  The first desgin
&lt;/h2&gt;

&lt;p&gt;Based on the results of my tiny survey, I then started to create a mockup of the template in Figma. I've been using Figma for a while now, both for my personal projects, as well as at my day job and got quite comfortable with it's features.&lt;/p&gt;

&lt;p&gt;Coming from Adobe XD it was super easy to transition to Figma, as both tools are pretty similar. One thing that makes me love Figma is the fact, that it can be fully used in the browser.&lt;/p&gt;

&lt;p&gt;To get some insipiration for the colors, I used &lt;a href="https://colorpalettes.colorion.co/"&gt;Actionable Color Palettes&lt;/a&gt;, decided for a color palette and tweaked the colors a tiny bit to meet the afforementioned a11y standards. For the contrast checking I usually resort to &lt;a href="https://colorable.jxnblk.com/"&gt;colorable&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;After sketching out the first draft, I decided, that it would be cool, to give people the opportunity to easily customize the accent color used in the template and thus decided to look for some more colors, that fit the overall look and feel of the design.&lt;/p&gt;

&lt;p&gt;As soon as I had something to show, I went back to twitter to showcase my work once more and get some feedback. The overall sentiment seemed to be very positive with minor suggestions in terms of content and increased whitespace in some places.&lt;/p&gt;

&lt;p&gt;I applied the feedback and finished the mockup. Again, I then tweeted the final result, announcing that I would be launching it as a free HTML/CSS/JS template soon after. The reactions were super positive and a lot of people showed interest in the product.&lt;/p&gt;

&lt;h2&gt;
  
  
  Finally coding
&lt;/h2&gt;

&lt;p&gt;So the next day I sat down and started implementing the portfolio in code. I coded everything from scratch in about 8 hours. The best thing? No dependencies! There's just an HTML, a CSS and a JS file and a few SVG graphics. I wanted something slim and easy to set up and customize. No heavy boilerplating, nothing. If you wanted, you could just open the HTML file in a text editor on your phone, replace the texts and you're ready to deploy.&lt;/p&gt;

&lt;p&gt;I launched it like 15 minutes after writing the last line of code on a saturday evening. Which in retrospect might not have been the best decission. But, I just wanted to get something out there finally! For the next launch I will definitely pick a better time (there are actually less users active on the weekend) and maybe review the code once or twice and let some people take a look at it beforehand.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happened next
&lt;/h2&gt;

&lt;p&gt;In 24 hours I gathered 103 views and 19 downloads on gumroad.&lt;br&gt;
Compared to the amount of people that priorly reached out to me and showed interest, it's not that much, but still I'm pretty satisfied with the results. Now almost a week later the product has 142 views and 28 downloads. Also one of them even decided to pay actual money for the FREE template, which is just mind blowing!&lt;/p&gt;

&lt;p&gt;In order to reach all those views and conversions I did several things. First, I DM'ed all of the people on twitter, who previously showed interest in the product. On top of that I reached out to some of my friends on twitter, asking if they would help spreading the word about the free template.&lt;/p&gt;

&lt;p&gt;So as you can see, I haven't done a lot of marketing for the product yet. The next steps will include writing better marketing copy, create marketing images and promote the template not only on twitter, but also on other platforms, such as facebook (especially developer groups on there) and reddit. Of cours, even this blog post is a way of marketing the template!&lt;/p&gt;

&lt;h2&gt;
  
  
  Next steps
&lt;/h2&gt;

&lt;p&gt;After I'm done with all of the marketing experiments, I will then work on transforming the template into a version to use with next.js (maybe also gatsby!) and on top of that I will create a full-fletched WordPress Theme from it. These will probably be paid products, but very low-price ( &amp;lt; $5.00 ). Also, of course there will be more template from me in the future! I plan on creating a template for SaaS-Products next. Also I plan on building an enitre UI library with a lot of page templates, layouts and examples. So stay tuned for that!&lt;/p&gt;

&lt;p&gt;Cheers&lt;br&gt;
Nathan&lt;/p&gt;

&lt;p&gt;You can find the free portfolio template for developers at &lt;a href="https://aptex.gumroad.com"&gt;aptex.gumroad.com&lt;/a&gt;!&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>beginners</category>
      <category>portfolio</category>
      <category>html</category>
    </item>
  </channel>
</rss>
