TheFrontEnd🔥. Страница 2
10926
@thefrontend
📝 Articles🗞 News 👓Tutorials 🤔 UI/UX thoughts
-
TheFrontEnd🔥
#tools #thoughts Aand yet another no-code-build-native-apps-fast-enough service, but this time somehow it feels more thoughtful than others. https://flutterflow.io/ So ios/android + out of the box firebase support for your backend seems neat. Anyone tried it? Any feedback? I generally smile at those, but that one kinda made me think "OK, if I need some quick prototyping or basic MVP might give it a go". Surely you still gonna need to learn it as any other tool really but that one looks like a week top. 
-
TheFrontEnd🔥
#uiux #tools #learn Alright now this is golden 10 🔥 out of 10. A whole list of assessments on design, UI and UX, tooling and whatnot. Just did a few and way too good https://app.uxcel.com/skill-tests 
-
TheFrontEnd🔥
#uiux Ah, why not. You've waited long enough for some activity here 😂 Basically a cool UX example from https://sentry.io/, right click on the logo (long press on mobile) and Sentry gives you a way to download all their variants of logo - transparent, dark, without text you name it. Think if every company had that a world would be a simpler place. Also, a side note to future self: wording on a cookie banner as "like every organisation on earth" for some reason builds trust. 
-
Реклама
-
TheFrontEnd🔥
#news 🎄 New year open-source giveaway Remember refine from the earlier posts? The open-source React-based framework for building CRUD apps rapidly. They are now celebrating the new year with the open source community and giving away: 🎁 $100 Amazon Gift Card to the raffle winner, 🎁 All three winners will get refine Swag Kit. For more details take a look at the following post: dev.to/necatio…kit-2f3e Winners will be announced on December 15 on Twitter. -
TheFrontEnd🔥
#uiux Most useful date picker. Imagine the frustration 😂 -
TheFrontEnd🔥
#tools Appodeal is a self-publishing platform that helps gaming studios establish and scale their mobile app businesses. Recently came across Appodeal’s news on its latest SDK update. Some cool stuff there including Appsflyer, Adjust and Meta Analytics being added to the SDK’s core, compliance tools being improved, distribution via the Unity Package Manager added, and more. Worth checking it out, some of the features might be what you’ve been looking for to level up your monetization. 🔗 Link 🕶 7 min -
TheFrontEnd🔥
#thoughts Fixed routing on the web apps? -
TheFrontEnd🔥
#uiux #games If you played GTA before (wait.. Who didn't?) Someone just added their radios to a Web in a similar UI, should work on any device, in case you want to bring some nostalgy to you coding sessions. https://play.smolyakov.dev PS it's in Russian, but you ll figure it out 
-
TheFrontEnd🔥
#learn Tech debt Something we all sooner or later have to deal with. In my experience it usually came down to either "rushing" features and deviating business model from what it was initially designed to do or complexities in "billing refactors" - some clients are difficult in understanding what's the point. Here I'm treating "rushing" inclusive of not doing anything, packages and tools getting outdated, deprecated etc based on the logic that if you were not rushing other things, you could properly address the refactors. Whereas the last point is fairly easy to resolve, just requires time and right arguments, the first one can bite in the future if left untouched. And personally I think its more about building the right mentality in a team. The concept thats highlighted in "Clean Code" by Robert C. Martin - if every developer when touching the part of the system leaves it in just slightly better shape than it was, we ll end up in constantly improving, almost self-refactoring system. Extending a feature? Maybe there is a way to improve type safety in the same file, maybe naming variable can be better, maybe function could have been splitted more logically, maybe you can rewrite something in a more concise syntax? - simple things like that, makes a difference in long term. Interesting article on that: 🔗 Link 🕶️ 8 min -
TheFrontEnd🔥
#learn 10 out of 10 🔥goodness in the house. Have you ever thought that React is just a mess? I know, I know, we all did at times. Below is a really interesting article on how things could have been done (or in fact already done in other unappreciated frameworks). Particularly interesting is what www.solidjs.com does - you get jsx-similarity, state, hooks, effects, life cycles, but all in a.. less annoying way than in React. Another one is www.markojs.com which I just call html on steroids. And finally www.hotwired.dev, which I've seen before, but noticed they are planning to soon release Strada, which suppose to ease the transformation of your Web apps into native mobile apps. Link to the article that's worth the read 🤓 -
TheFrontEnd🔥
#tools The open-source React framework now has built-in support for Mantine. All Mantine UI components and hooks are exported from refine to build rock-solid CRUD apps.⚡️ GitHub Link: https://github.com/refinedev/refine 
-
TheFrontEnd🔥
#thoughts www.layoffs.fyi - someone created a trackable, filterable layoff tracker since Covid 19. Maybe can be an interesting find when you thinking which companies to send your resumes to. 
-
TheFrontEnd🔥
#tools Antoher one to you Swiss toolset in addition to Planby. www.tremor.so - fairly new UI lib for dashboards, charts and graphs. Looks pretty neat, only wish they keep it "dashboard-focused" and push into that direction. PS as a bonus on charts you get smooth mounting animation, which some of the other chart libs don't offer out of the box. 
-
TheFrontEnd🔥
#uiux Refine A 100% open-source, headless React framework (5.2K Stars on GitHub) for CRUD apps, so you can quickly build admin panels and dashboards while still remaining flexible.✨ Refine seamlessly works with any custom design or UI framework you favor. For convenience, it ships with ready-made integrations for Ant Design System, Material UI, Mantine, and Chakra UI 🚀 
-
TheFrontEnd🔥
#uiux Just found Planby - a cool React component for building timelines like on the screenshot. This can be pretty powerful lifehack when implementing calendar-like functionality. I had a pleasure of implementing something similar myself and the critical part there is rendering performance, especially when dealing with huge datasets. My personal learning was pagination / data limitation is the key. In grid data visualisations you ll most likely end up using either infinite scrolling (both vertical and horizontal) or filtering (aka show only this week's worth of data etc). Or both 😂 Either way, wish I had that lib to play around first before I did everything myself. PS accessed it on mobile and was pretty smooth also 
-
Реклама
-
TheFrontEnd🔥
-
TheFrontEnd🔥
Why We're Breaking Up with CSS-in-JS - DEV Community 👩💻👨💻 dev.to/srmagur…-js-4g9b -
TheFrontEnd🔥
#thoughts We vs I I see a lot of small channels on telegram using typical corporate invention and say "We" anytime they share something. "Today we prepared for you.." "We were quite busy lately" "We found this cool tool.." You get the idea. It's totally understandable to have that in some work environments (especially where teamwork is valued more than individual achievements). But when it comes to your personal projects, blogs, channels, personal websites etc not only I find it weird, but also damaging. People do that to create a mental protection and share responsibility if something goes wrong (eg they've made a mistake or were completely wrong in what they shared). Also it makes it sound like the statement is more valid (which is just a bandwagon fallacy). The only problem is that if you are on your own there is noone to share that responsibility with, pretending that you have a team of 20 people behind you is useless as this would just bump up expectations that you ll likely won't meet. There is absolutely nothing wrong in saying "I" like in examples above, especially if you doing something on your own. In fact, despite corporate bullshit it makes things more personal, cosy and simple, helping to set the right expectations with the crowd. Rule of thumb unless you are in corporate ecosystem. Was it just you involved in it? Yes - use "I" No - use "We" Keep things simple in a not so simple world 🫡