Web development trends 2020

Here are some web trends for 2020:

Responsive web design in 2020 should be a given because every serious project that you create should look good and be completely usable on all devices. But there’s no need to over-complicate things.

Web Development in 2020: What Coding Tools You Should Learn article gives an overview of recommendations what you learn to become a web developer in 2020.

You might have seen Web 3.0 on some slides. What is the definition of web 3 we are talking about here?
There seems to be many different to choose from… Some claim that you need to blockchain the cloud IOT otherwise you’ll just get a stack overflow in the mainframe but I don’t agree on that.

Information on the web address bar will be reduced on some web browsers. With the release of Chrome 79, Google completes its goal of erasing www from the browser by no longer allowing Chrome users to automatically show the www trivial subdomain in the address bar.

You still should target to build quality web site and avoid the signs of a low-quality web site. Get good inspiration for your web site design.

Still a clear and logical structure is the first thing that needs to be turned over in mind before the work on the website gears up. The website structure for search robots is its internal links. The more links go to a page, the higher its priority within the website, and the more times the search engine crawls it.

You should upgrade your web site, but you need to do it sensibly and well. Remember that a site upgrade can ruin your search engine visibility if you do it badly. The biggest risk to your site getting free search engine visibility is site redesign. Bad technology selection can ruin the visibility of a new site months before launch. Many new sites built on JavaScript application frameworks do not benefit in any way from the new technologies. Before you go into this bandwagon, you should think critically about whether your site will benefit from the dynamic capabilities of these technologies more than they can damage your search engine visibility. Well built redirects can help you keep the most outbound links after site changes.

If you go to the JavaScript framework route on your web site, keep in mind that there are many to choose, and you need to choose carefully to find one that fits for your needs and is actively developed also in the future.
JavaScript survey: Devs love a bit of React, but Angular and Cordova declining. And you’re not alone… a chunk of pros also feel JS is ‘overly complex’

Keep in mind the recent changes on the video players and Google analytics. And for animated content keep in mind that GIF animations exists still as a potential tool to use.

Keep in mind the the security. There is a skill gap in security for many. I’m not going to say anything that anyone who runs a public-facing web server doesn’t already know: the majority of these automated blind requests are for WordPress directories and files. PHP exploits are a distant second. And there are many other things that are automatically attacked. Test your site with security scanners.
APIs now account for 40% of the attack surface for all web-enabled apps. OWASP has identified 10 areas where enterprises can lower that risk. There are many vulnerability scanning tools available. Check also How to prepare and use Docker for web pentest . Mozilla has a nice on-line tool for web site security scanning.

The slow death of Flash continues. If you still use Flash, say goodbye to it. Google says goodbye to Flash, will stop indexing Flash content in search.

Use HTTPS on your site because without it your site rating will drop on search engines visibility. It is nowadays easy to get HTTPS certificates.

Write good content and avoid publishing fake news on your site. Finland is winning the war on fake news. What it’s learned may be crucial to Western democracy,

Think to who you are aiming to your business web site to. Analyze who is your “true visitor” or “power user”. A true visitor is a visitor to a website who shows a genuine interest in the content of the site. True visitors are the people who should get more of your site and have the potential to increase the sales and impact of your business. The content that your business offers is intended to attract visitors who are interested in it. When they show their interest, they are also very likely to be the target group of the company.

Should you think of your content management system (CMS) choice? Flexibility, efficiency, better content creation: these are just some of the promised benefits of a new CMS. Here is How to convince your developers to change CMS.

html5-display

Here are some fun for the end:

Did you know that if a spider creates a web at a place?
The place is called a website

Confession: How JavaScript was made.

Should We Rebrand JavaScript?

2,294 Comments

  1. Tomi Engdahl says:

    https://www.fraktio.fi/blogi/remix-framework-askel-taaksep%C3%A4in

    Remix-framework – askel taaksepäin
    TL;DR
    Kautta aikain web-kehitys on rakentunut web-standardien päälle.
    JavaScriptin myötä sisältöä voitiin luoda ja muuttaa dynaamisesti lataamatta sivua uudelleen. Samalla hylättiin web-standardeihin jo toteutetut tavat tehdä kyseiset asiat.
    Hakukoneet eivät tykänneet tästä, eivätkä myöskään korkean suorituskyvyn vaativat palvelut, sillä nyt samat asiat piti suorittaa käyttäjän selaimessa.
    Web-kehityksessä palattiin palvelinpohjaiseen malliin, jolloin käyttäjän selaimessa suoritettavaa koodia oli vähemmän. Tämä parantaa suorituskykyä ja saavutettavuutta verrattuna pelkästään JavaScript-pohjaisiin ratkaisuihin.
    Remix on paluu takaisin web-kehityksen juurille. Remix noudattaa web-standardeja, vähentää ylläpidettävää koodia ja toimii alustariippumattomasti.

    Remix tarjoaa paremman kehityskokemuksen kuin esimerkiksi Next.js keskittyen taaksepäinyhteensopivuuteen ja yksinkertaisuuteen.

    Reply
  2. Tomi Engdahl says:

    In 2019, Facebook (now Meta) developed a feature for the Facebook Pixel called Automatic Advanced Matching (AAM). The website owner states that they activated the AAM feature by mistake, which is the main reason their website unlawfully transferred that “huge” amount of personal data to Facebook/Meta, including social security numbers, bank account numbers, and other highly sensitive information.
    The website owner also activated a Meta Pixel feature called Automatic Events. Also this was done “by mistake”.
    While the company had approved its marketing department’s use of the Facebook Pixel, which was implemented after an internal security and compliance process, it had not approved the AAM or AE features.

    The marketing department later asked the legal department for approval to use the specific AAM feature for the Meta Pixel, which the latter denied. Despite this, someone had turned on the AAM feature.
    What does Meta’s AAM feature do?
    The AAM (Advanced Automatic Matching) feature enables a website that uses the Meta Pixel to automatically collect visitors’ data and match them with users on their platforms—Facebook and/or Instagram.

    If you use a form on your website, AAM collects form-data like email addresses and phone numbers and sends this to Facebook/Instagram. The data is hashed for security reasons before it is transferred.
    The purpose is to track and profile visitors so that your ads can be more accurate and effective.

    The AE (Automatic Events) feature enables a website that uses the Meta Pixel to automatically track user interactions, such as button clicks, searches, and menu selections.

    What happened when the website owner activated the Meta Pixel?
    When the website owner, in this case unknowingly, activated the AAM and AE features, they ended up sharing personal information with Meta en masse.

    Did every website visitor risk getting their personal information transferred to Meta?
    No, “only” those who had consented to marketing cookies on the site and had logged into the site got their movement tracked by the Meta Pixel and their personal data shipped to Meta.
    With one exception.
    Some buttons for certain forms on the website were bare for all visitors, targeting visitors who were not customers of the company. Visitors who filled in those fields and pushed those buttons would also get their data transferred to Meta, specifically due to the AE feature of the Meta Pixel being activated.

    Why was the website owner fined for using the Meta Pixel?
    They were not.
    The Swedish DPA does not audit if you have breached the ePrivacy-directive, sometimes dubbed “the cookie law”. The enforcement authority for that is the Swedish Postal and Telecom Authority.
    So what was this case about, then?
    In this specific case, the DPA explicitly states that they only looked at how personal data was collected and then shared with a third party and whether this was in breach of the GDPR.
    The DPA did consider whether there were legal grounds, such as consent, for collecting the data. They do, for example, write that only (mostly) visitors who had consented (on a cookie banner, one must presume) to marketing cookies (and then logged into the website as a customer) had gotten their data collected and shared with Meta without scrutiny

    https://cookieinformation.com/resources/blog/is-the-meta-pixel-gdpr-compliant/

    Reply
  3. hire android app developer says:

    I recently worked with an Android app development company, and I am thoroughly impressed with their services. Their team was highly skilled, professional, and attentive to my needs. They developed a custom Android app that exceeded my expectations, both in functionality and design. The project was completed on time, and their post-launch support has been excellent. I highly recommend them for anyone looking for top-quality Android app development.

    Reply
  4. Tomi Engdahl says:

    Meet Toddle: the Next Open Source Web App Builder
    We check out Toddle, a web app builder that focuses on a component hierarchy for the frontend, with adoption of data at the backend.
    https://thenewstack.io/introduction-to-toddle-soon-to-be-open-source-web-app-builder/

    Reply
  5. Tomi Engdahl says:

    https://www.facebook.com/share/p/UqveiVKwXbsFoNLy/

    Sorry to disappoint, but the cookie was not meant to be related to a HTTP cookie or a programming “in joke”. There is a lot of symbolism in the cookie, but it wasn’t this.

    HTTP cookies were around since 1994, but the concept of having to be aware of and “accept” cookies did not come into being until long after The Matrix.

    The concept of being told about and then having to “accept” cookies (informed consent) didn’t become a thing until the EU Cookie Directive in 2009. Before the EU regulatory actions, you just got them whether you wanted them or not. It was a full decade after the release of The Matrix that the concept of “having to accept” cookies came into being.

    The Matrix cookie has been said to symbolize many things, including free will, code injection, etc., but it was not a nerd “in joke” reference to web cookies.

    But facts don’t really go viral.

    Reply
  6. Tomi Engdahl says:

    Matt Mullenweg: ‘WordPress.org just belongs to me’
    The lines between the WordPress open-source project, the nonprofit backing it, and the commercial arm owned by Automattic are blurring.
    https://www.theverge.com/2024/10/4/24262232/matt-mullenweg-wordpress-org-wp-engine

    Over the past several weeks, WordPress cofounder Matt Mullenweg has made one thing exceedingly clear: he’s in charge of WordPress’ future.

    Mullenweg heads up WordPress.com and its parent company, Automattic. He owns the WordPress.org project, and he even leads the nonprofit foundation that controls the WordPress trademark. To the outside observer, these might appear to be independent organizations, all separately designed around the WordPress open-source project. But as he wages a battle against WP Engine, a third-party WordPress hosting service, Mullenweg has muddied the boundaries between three essential entities that lead a sprawling ecosystem powering almost half of the web.

    Reply
  7. Tomi Engdahl says:

    Server-side tagging ja tracking PK-yritysten näkökulmasta: Tarpeellinen investointi vai ylimitoitettu ratkaisu?
    https://jatkotarina.fi/server-side-tagging-ja-tracking-pk-yritysten-nakokulmasta/

    Server-side tagging ja tracking ovat nousseet verkkoanalytiikan keskusteluissa trendikkäiksi aiheiksi. Nämä termit ja niiden sisällöt menevät kuitenkin keskustelijoilla melko iloisesti keskenään ristiin. Tässä artikkelissa näistä termeistä puhutaan lyhenteellä SST, jolla tarkoitetaan ylätasolla molempia tekniikoita menemättä sen syvemmälle siihen, miten ne toisistaan poikkeavat.

    SST:ä markkinoidaan usein välttämättömänä ratkaisuna moderniin verkkoanalytiikkaan, erityisesti AdBlockereiden ja tiukentuvien yksityisyysasetusten vuoksi. Siitä on tullut trendisana, jolla kaikki markkinointialan toimijat pyrkivät erottautumaan joukosta. Jos olet verkkoliiketoiminnasta vastaava päättäjä, olet todennäköisesti jo kohdannut näitä myyntipuheita väsymiseen asti. Tämän artikkelin tarkoitus on auttaa sinua asettamaan myyntiargumentit oikeaan perspektiiviin yrityksesi tarpeisiin nähden.

    SST on verkkoanalytiikan toteutustapa, jossa toisin kuin perinteisessä analytiikassa, data ei kulje suoraan selaimesta analytiikkapalveluihin (kuten Google Analytics, Matomo, Piwik Pro). SST mahdollistaa datan käsittelyn ja muokkaamisen yrityksen palvelimilla ennen sen lähettämistä eteenpäin.

    Ilman SST:ä menetät dataa – mutta haittaako se?
    SST kiertää monia perinteisen seurannan rajoitteita: vältetään AdBlockerien vaikutukset, selaimien kiristyviä yksityisyysasetuksia, ja dataa katoaa vähemmän. Mutta pysähdytään hetkeksi miettimään – mitä tämä käytännössä tarkoittaa PK-yritykselle?

    Verkkoanalytiikan data ei koskaan ole täydellistä. Kaikkia käyttäjiä ei tulla ikinä saamaan analytiikan työkaluilla kiinni, eikä käyttäjien eri käyntikertoja pystytä koskaan aukottomasti linkittämään toisiinsa, eli käytännössä liiketoimintapäätöksiä tehdään aina epätäydellisen tiedon pohjalta.

    on tärkeintä ymmärtää, miten paljon dataa menetät. Jos dataa hukkuu 20 %, tilanne on todennäköisesti aivan hallinnassa. Jos dataa taas hukkuu 60 %, lienee syytä tehdä jotain.

    Datan menetys ei siis ole automaattisesti ongelma. Oleellista on tietää, missä kohtaa dataa katoaa ja miten se vaikuttaa päätöksentekoon. SST ei ole yleisratkaisu kaikkiin analytiikan ongelmiin, vaan työkalu, joka pitää räätälöidä vastaamaan juuri sinun yrityksesi tärkeimpiä tiedontarpeita.

    Tietosuoja ja GDPR – onko SST välttämätön?
    Tietosuojakysymykset ovat kriittisiä, mutta ne voidaan ratkaista myös perinteisemmillä työkaluilla. Google Tag Manager mahdollistaa datan anonymisoinnin jo keräysvaiheessa, ja EU-pohjaisten analytiikkatyökalujen (kuten Matomo tai Piwik Pro) käyttö ratkaisee huolet datan tallentumisesta EU-alueen rajojen sisäpuolelle. Jos haluat välttää Googlen työkalut kokonaan, voit Googlen Tag Managerin sijasta totta kai käyttää myös Matomon tai Piwik Pron omaa tag manageria. SST ei siis tuo tietosuojaan merkittävää lisäarvoa useimmille PK-yrityksille.

    Huomaa, että myös SST toteutuksen pitää totella käyttäjän suostumusta evästeiden ja henkilökohtaisen datan käyttämiselle mainonnan kehittämiseen. Eli mikäli käyttäjä kieltää evästeiden tai henkilökohtaisen datan käytön, ei myöskään SST voi niitä hyödyntää. Et voi kohdentaa käyttäjään uudelleenmainontaa tai seurata palaavia käyttäjiä SST:llä sen enempää kuin perinteisemmilläkään ratkaisuilla.

    Suorituskyky – marginaalista optimointia?
    SST:n vaikutus sivuston suorituskykyyn on fakta. SST:n myötä käyttäjän selaimesta siirtyy palvelimen kontolle nippu tehtäviä, jotka nopeuttavat sivuston toimintaa käyttäjän selaimessa. Useimmille PK-yrityksille tämä optimointi on kuitenkin sama, kuin ostaisi Ferrarin työmatka-ajoon – teknisesti parempi ratkaisu, mutta ei ehkä se ensimmäinen asia, joka tulisi toteuttaa. Harvan yrityksen verkkopalvelu on teknisesti jo valmiiksi siinä kunnossa, että SST teknologiaan investoiminen suorituskyvyn parantamiseksi olisi järkevämpää kuin sivuston tekniikan muu parantelu.

    Ennen SST:hen investoimista PK-yrityksen päättäjän kannattaa kysyä alla olevat kysymykset itseltään ja niiden pohjalta arvioida SST-järjestelmän tarvetta.

    Onko nykyinen analytiikkadata riittämätöntä liiketoiminnan kehittämisen kannalta?
    Pystyykö nykyistä analytiikkajärjestelmää kehittämään helposti riittävälle tasolle ilman SST-teknologiaan turvautumista?
    Onko meillä jokin tietty tarve, mihin tarvitsemme dataa, jota vain SST pystyy tuottamaan?
    Onko meillä resurssit ylläpitää ja kehittää SST-ratkaisua?
    Ymmärrämmekö varmasti, mitä olemme hankkimassa, ja mitä sillä saadaan?
    Verkkoliiketoimintojen ja -analytiikan kehittäminen on pitkäjänteistä työtä – ei yksittäinen projekti tai teknologiainvestointi.

    Reply
  8. Tomi Engdahl says:

    Paresh Dave / Wired:
    Rival search engines Ecosia and Qwant launch European Search Perspective, a joint venture to develop an index of the web to reduce reliance on Google and Bing

    https://www.wired.com/story/ecosia-qwant-eusp-take-on-google-search-index/

    Reply
  9. Tomi Engdahl says:

    Emma Roth / The Verge:
    Google says it will test removing news articles from EU-based publishers from Search for 1% of users in France, Poland, Italy, Spain, and other EU countries

    Google is testing the ‘impact’ of removing EU news from search results
    / The test will show publishers how much traffic they’d miss out on without Google.
    https://www.theverge.com/2024/11/13/24295463/google-eu-test-news-outlets-removing-results

    Reply
  10. Tomi Engdahl says:

    How an HTTP Request Gets Served – In Great Detail
    https://www.youtube.com/watch?v=hWyBeEF3CqQ

    Dave describes the entire chain of events that happens when you enter a URL into your browser, from the DNS resolution to the GPU displaying the bits on your screen, with nothing left out of the middle!

    Reply
  11. Tomi Engdahl says:

    https://nighteye.app/
    Protect Your Eyes!
    Enable dark mode on any website.

    Reply

Leave a Reply to Tomi Engdahl Cancel reply

Your email address will not be published. Required fields are marked *

*

*