Hi there, there’s been quite some time since the last update @Codete Team blog took place, but here we come again. This time, we’re gonna revive the blog by several warm-up entries, covering, unlike it was until the now-finished hiatus, the IT-related topic wider.
The first entry will be therefore devoted to frontend development. Yes, in general, frontend, but in certain relevance to Codete’s developments so far. To introduce the topic, and not refer all of those who find the technical term unintelligible – no shame there! – to Wiki or Google, we’ll say a few words. Then, the plan is to move forwards to some of the Codete’s latest developments and to mention the frontend development solutions applied there, with just few words of elaboration. Sound good enough to you? Well, then, let’s go!
So, what is frontend, anyway? To get the gist of this notion, it’s best to consider a pair of complementary opposites – frontend and backend. They are a little bit like software and hardware. Actually, front and back end create a little bit of analogous division within the software itself. Backend is like the hardware of software – the guts that make the engine of it all. Frontend, on the other hand, is guts, too – it’s code, after all – but it’s directly responsible for the interface aspect of any software. So, know this – whenever you complain about a program crashing down, it’s backend’s fault – but when things run well, but operating a given programme is a nightmare, or, on the other hand, the experience overwhelms you with its smoothness – it’s due to a frontend development well done.
Of course, the more applications there are, the more competitive the market is, the more the frontend requirements rise. Now app development – be it web or mobile – has to consider usability and design as driving forces of any sensible development. And when usability kicks in, certainly it’s the frontend developers that will have more in their plate. Just consider A/B testing, which by definition at the outset takes two different app layout versions and puts them to the test to determine which one is proven to be better, based on real user behavior.
Frontend example from Codete portfolio
Moving on to the next section of this entry, let’s briefly discuss some of the Codete’s developments and their frontend layer. Several entries ago – you may need to click “older posts” in the main page column – we introduced an app for monitoring world tweeting tendencies in real time. For some of our readers, being more into code than social media stuff, may react “why twitter?” we need to explain. Should any of you ever worked for a media company, or, better yet, in a newsroom, it’s where Twitter reveals its full power and importance. Happens that foreign press agencies are first to break certain news, and it takes time until the local one will report, be it even Reuters. Twitter allows you to reach the source. Tweeting trends are excellent material for seeing the upcoming waves, the local hot trends, and the news that prove the most retentive in the public eye. This application is a perfect example of using simple, yet proper, tools to deliver exactly what was needed. We have a great variety of tools at our disposal when determining which would be the best for a given project. Starting with big frameworks like React, Vue.js or Angular, libraries containing Redux and Material-ui and ending with well known 3rd party services like Google Maps. Proper toolset sometimes makes a difference between good and bad user experience.
Bonus: call for frontend pioneers!