Volodymyr Pylypchatin

Most Magento merchants still think Hyvä migration must be “all-or-nothing”. That’s not true. At Meet Magento Poland, I realized something surprising: 👉 Many merchants and even agencies don’t know that Hyvä theme can be rolled out page by page, not as one huge, expensive, long-running project. The reality: You don’t need to migrate the entire Magento store at once to start getting value from Hyvä. Thanks to Hyvä’s Luma fallback, you can: 1️⃣ migrate only the homepage first 2️⃣ then roll out Hyvä by page type, based on priority, for example: - product pages - checkout - category pages - CMS pages - account area, cart, etc. Why this approach is powerful: ✔️ Immediate ROI - performance, CRO & SEO benefits start from day one ✔️ Lower risk - no “big bang” launch ✔️ Flexible budgets - spread investment over time ✔️ Business-driven prioritization - migrate what impacts revenue first Such an approach has already been successfully used on many Magento stores. In practice, it’s usually done per page type, not per single page, which makes it even more efficient. Yet this approach is still massively undercommunicated in the Magento ecosystem. If you’re running Magento and: ✔️ want Hyvä performance without waiting months ✔️ want to improve conversion rate and SEO results step by step ✔️ want a migration strategy aligned with business impact, not just tech …then Hyvä doesn’t have to be a “one big leap” project. Happy to share real-world insights, pitfalls, and how to structure this correctly - feel free to comment or DM. #Magento #Hyva #HyvaTheme #MagentoPerformance #MagentoCRO #EcommerceGrowth #MeetMagento #ThoughtLeadership #MagentoAgency

38

3 komentarze

Vibe coding, a term coined by Andrej Karpathy in February 2025, describes an increasingly popular approach to writing software: express the code you want in a few sentences to an AI system like ChatGPT or Claude, then polish and (hopefully!) test the generated result. Two things you should know: 1) Vibe coding isn't new, but the name is. 2) Vibe coding doesn't eliminate work—it just shifts it from writing to explaining and reviewing... which isn't always a win. With vibe coding, you're playing archeologist in someone else's mistakes. For better or worse. In my newsletter, I walk you through an example and present the case for vibe coding and the case against it, analyzed from the POVs of the novice and the expert. Read my full explanation here: https://lnkd.in/e4_RS4fD #AI #vibecoding #technology #GenAI #software #programming #coding If you found this useful, a repost and follow makes my heart happy.

500

75 komentarzy

Markus Ingvarsson delivered an inspiring session at JS Poland 2025: Bring Your Own Model using Transformers.js. He guided the audience on how to run custom AI models directly in JavaScript apps, leveraging Transformers.js for browser-based intelligence—no backend required! A valuable hands-on deep-dive for developers looking to add state-of-the-art AI to their web projects. #jsPolandConf

36

2 komentarze

#CoreWebVitals is ±85% frontend. So there's more than CWV: TTFB, hosting and caching! → TTFB is the first and most important metric → Ask any WP, Magento Association, Shopware etc site owner, they will know 😜 → And that's why both solid hosting and optimal (server side) caching strategy is important 𝐓𝐞𝐬𝐭𝐢𝐧𝐠 Nevertheless, most are still screwing up their real #TTFB as they limit testing to: → a single location → server cached pages (=skewing results) → fixed URLs instead of testing with all possible query strings In other words, in reality there are (too) many conditions that will dictate real life TTFB. 𝐀 𝐫𝐞𝐚𝐥 𝐞𝐱𝐚𝐦𝐩𝐥𝐞 Monitoring and collecting those conditions will then allow you to not just see the result of a single (or repeated) synthetic test, but data of real pageviews under real conditions. Attached is an example of an audit I'm doing today. And to prevent drawing incorrect conclusions, I've specifically zoomed into the server response time. This is what we're seeing: 1️⃣ gclid + gad_source is traffic coming from #GoogleAds etc 2️⃣ but those are clearly the ones with a worse TTFB (=white screen for a longer time) 3️⃣ so this merchant isn't only paying for this traffic, they are also less likely to convert 4️⃣ meaning this is very expensive traffic, both from a revenue and server load perspective 5️⃣ and hurting your #PPC as the Quality Score drops Looking at the coloured horizontal bars, requests with a query string are clearly lacking some green/good experiences. In other words, Google Ad traffic never leads to a good server response time and is probably never hitting the Varnish nor CDN cache 😬 𝐑𝐔𝐌𝐯𝐢𝐬𝐢𝐨𝐧 When using RUMvision - Core Web Vitals monitoring, you can easily track the server side caching status of pages as well when using: → Varnish (thanks to our hosting partners for exposing this info) → CDN (Shopify & Cloudflare exposing it out of the box) Very convenient to collect that as well using Server-Timing (offered out of the box) when debugging TTFB!

22

2 komentarze

Dev teams often mistake surface polish for strategic clarity. ​​A sleek UI might win design awards, but if it’s built on shaky assumptions, it’s just an expensive mirage. If your idea is going to support real users, scale with your business, and withstand inevitable pivots, it needs more than aesthetics. It needs structure. It needs a blueprint. If a project kicks off without a validated plan that accounts for business goals, user needs, tech constraints, and delivery realities, things can go sideways fast. A presentation slide is made to sell an idea. A blueprint is made to build it. ❌ Slides don’t clarify scope. ❌ They don’t define trade-offs. ❌ They don’t align delivery teams with decision-makers. A blueprint does all of that and ensures that every hour spent building moves you toward something that works, lasts, and supports the business. At Mavric, we believe innovation should serve your business, not the other way around. Our role is to bring strategic thinking and technical expertise to your vision, staying grounded in your goals every step of the way. Strategy beats sizzle in every successful software build. Build it right, or don’t build it at all. Are you building from a blueprint or a pitch deck? #productstrategy #softwaredevelopment #digitaltransformation #buildbetter

30

Magento 2.4.8 has been released. What's critical for merchants to know? Most changes are under the hood, but with two BIG exceptions 😃. Background changes: => PHP 8.4 support: more features to make your dev team faster. => Goodbye PHP 8.1: after all, this is officially unsupported in December 2025. => Security improvements (improved encryption key management thanks to CosmicSting) => New supported versions of MariaDB and MySQL Cool updates: => Significant improvements to GraphQL (thanks to Optimizer push) => Braintree: package tracking and items included in Apple Pay/Google Pay => (BIG) B2B: frontend administrators can manage their own company hierarchy. This was previously a massive gap in B2B. => (BIG) B2B: sellers can attach document links (DocuSign and Adobe Sign) directly into a quote template. #magento #adobecommerce

313

18 komentarzy

When coding meets passion again… 🔥 Recently, while leading a large-scale Magento project at Caliente iTech, I found myself deeply aligned not only with the client's goals but also with the way the previous frontend architecture was crafted. As I reviewed their frontend & backend code structure and guidelines laid by the previous agency, I had one word in mind: "Respect" It was almost like seeing a mirror of how I’ve always trained my team to work… Clean. Scalable. Detailed. Intentional. It reminded me again why Magento development is not just about shipping features, it’s about crafting experiences, respecting structure, and valuing the micro detailing that often goes unnoticed. What makes it even more satisfying is that we’re now leading this project forward - continuing with the same discipline, and further pushing the boundaries of what’s possible. We aligned as a team on some core work values, and I believe these should be non-negotiable for any serious Magento team: ✅ Everything matters - even a single line of layout.xml ✅ Invest more time in R&D, estimation & planning than blindly jumping into code ✅ Stay in full communication with your team & client ✅ Be precise - deliver what you promised, in the timeframe promised ✅ Ensure proper local testing before anything goes live ✅ Respect and follow Magento’s coding standards ✅ Be detail-obsessed - each .less line, each phtml, each block ✅ Bring energy and enthusiasm to your work - your code reflects it Magento has always been a canvas for me, and with this project, it felt like painting again, not just coding. I feel proud to be back in that zone, leading a project that matches my thought process, depth, and development ethics. At Caliente iTech, we don't just build eCommerce solutions - we build precision-driven, scalable, and performance-focused digital commerce. If you’re in Magento, eCommerce, or leading a brand that cares about scalable architecture, let’s connect, discuss, and grow together. 🚀 #Magento2 #eCommerce #MagentoExpert #CalienteTech #MagentoDevelopment #AdobeCommerce #MagentoArchitecture #JewelleryEcommerce #LuxuryEcommerce

17

3 komentarze

Most founders think their biggest competitor is another startup. Actually, it’s their own perfectionism. In March, a founder reached out to me. His MVP was 80% ready. But he kept adding features. “Just one more integration” “The UI needs polish” “Let me add this analytics dashboard” 6 months later? Still no launch. Meanwhile, his competitor shipped a basic version. Got 27 paying customers. Used their feedback to build exactly what users wanted. Perfectionism feels productive. But it’s procrastination in disguise. Your first version will embarrass you. Ship it anyway. Because while you’re perfecting features nobody asked for someone else is solving real problems. Getting real feedback. Making real money. The market doesn’t care about your perfect code. It cares about solved problems. Ship at 70%. Learn from users. Iterate based on data, not assumptions. Your biggest competitor isn’t who you think. It’s the voice saying “it’s not ready yet.” P.S. What feature are you perfecting that nobody asked for?

18

21 komentarzy

I still remember the project… that changed how I see frontend vs backend forever. At first, it felt like a typical debate: Frontend devs argued about UI polish. Backend devs argued about scalable logic and APIs. Everyone was busy “winning” their side… until the bugs started piling up. ❎ Features broke. ❎ Users got frustrated. ❎ Deployments slowed. That’s when I realized the truth: The real problem wasn’t frontend or backend. It was the invisible battlefield between them, integration, async flows, mismatched APIs, and miscommunication. Most developers never see this. They focus on layers, not the system as a whole. But when teams start thinking full-stack, systems-first: ✅ Bugs drop ✅ Deployments speed up ✅ Users get seamless experiences This carousel dives into why 90% of devs miss the real problem and how bridging the gap changes everything. Swipe to see the hidden truth that transforms projects.

43

62 komentarze

Occasionally, we see vendors significantly downplay the severity of vulnerabilities. When we encountered a vulnerability in Magento (CVE-2025-54236), we observed that Adobe had made a significant effort to downplay the advisory’s criticality. Adobe’s official explanation for the impact of this CVE was described as: “an issue in Adobe Commerce where an attacker could take over customer accounts through the Commerce REST API”. Thankfully, a strong community of defenders in the Magento community flagged that this CVE was much more critical than Adobe made it out to be, leading to pre-authentication RCE. A huge thank you to the original finder of the vulnerability (Daniel👨‍🌾 Le Gall) and Sansec - experts in eCommerce security for highlighting how serious the issue really is and naming it the SessionReaper bug: https://lnkd.in/gJpuQh2V Technically, Adobe isn’t lying… It does let you take over customer accounts… but it also enables you to execute arbitrary code on the system?! As a debut of our new Security Researcher hire, Tomais Williamson diligently worked through reverse engineering this vulnerability, and has published his research on Searchlight Cyber’s blog today: https://lnkd.in/gqpzafry He’s put in some effort to help future researchers better understand the deserialization concepts inside Magento’s API and how it’s a massive footgun that should be monitored very closely in the future for security issues.

174

2 komentarze

In the early days of Magento, we saw how open-source technology didn’t just create a product; it built an ecosystem. Developers, businesses, and partners came together to collaborate, innovate, and grow something much bigger than any one company. Now, with AI reshaping industries and workflows across the board, we’re at a similar crossroads. What excites me isn’t just the innovation itself, but the shift in strategy—how key players like Meta are using open models like Llama to democratize AI and accelerate progress for everyone. Rather than hoarding resources behind a walled garden, they’re providing tools that empower a new wave of entrepreneurs, researchers, and operators to push the boundaries of what’s possible. It’s a strategy that reminds me of how open-source ecommerce once unlocked new opportunities at scale. As an investor, I’m drawn to this approach. It’s not just about building great technology—it’s about fostering ecosystems, enabling global collaboration, and driving innovation that benefits everyone. The next great “Magento moment” in AI isn’t just about technology; it’s about creating a platform for others to build on. And just as it worked before, this open, collaborative strategy is proving to be a powerful way forward for the future of AI and beyond.

66

8 komentarzy

Still think Magento is an enterprise-only powerhouse? Think again. Last year, a British boutique jewelry shop encountered a significant issue with its outdated eCommerce platform. Site crashes and generic shopping experiences were holding them back. Worried Magento was too much, they decided to try it anyway. After weighing the risks, they migrated to Magento instead of rebuilding from scratch. In only three months: → Product pages finally expressed their story → Checkout was effortless → Personalized recommendations led to a 35% increase in conversion rate During the holiday rush, the site experienced record traffic without issue, and the owner finally slept. Now, it's growing faster than ever. Magento was the platform that could finally sustain their ambition ● Features that other platforms put behind paywalls or didn’t offer at all were now in their hands. ● As traffic and sales grew, costs stayed predictable: no fees, no need to switch platforms down the road. If you’re aiming for real growth, choose a platform that grows with you. Magento lets you build, scale, and customize far beyond the basics, empowering your business not just today, but for years to come. The question isn't, "Is Magento too big for me?" but, "When will my business be too big to settle for less?" #eCommerce #Magento #DigitalGrowth #SMB #ScaleSmart #Magento2

7

In Ascentic we work mainly with Flutter and React Native in cross platform mobile app projects for our customers, but we also build with MAUI. If you have worked with all three of these, you might wonder - but why?   MAUI, Microsoft's cross-platform framework for creating native mobile and desktop apps with C# and XAML, is a quite young framework that still has some maturing to do before it becomes a truly compelling alternative to other frameworks. However based on your context, there are already today some reasons why it might be worth to consider:   👉🏽 You already have a .NET team and want to extend your platform with mobile apps for certain use cases - choosing MAUI can be a good way to get the work done without having to invest in a full new team of mobile devs   👉🏽 Native performance, single project - MAUI apps run on native platform runtimes and use the actual platform UI controls, delivering closer-to-native performance and look-and-feel than many hybrid approaches. Plus, you only maintain one project across iOS, Android, Windows, and macOS   👉🏽 Backed by Microsoft - for companies that care about long-term stability, MAUI is part of the broader .NET ecosystem. With Visual Studio integration, official support, and a long-term roadmap, it’s a safer bet for organizations looking for continuity   So yes, even though MAUI is likely give your development team some headache to start, it's still an option worth to consider.   Ps. if you want to learn more about MAUI - don't miss our next Fika webinar happening September 11th. Link down below.    #crossplatform #mobile #web #desktop #MAUI

166

4 komentarze