Nar Kumar Chhantyal

Will WordPress and TYPO3 developers become obsolete if a company switches to Storyblok? This is one of the most frequent concerns in our consulting calls. But there's no need for concern - shifting to Storyblok doesn't make these roles obsolete, it just changes their focus. They’ll have fewer worries about CMS security and chasing PHP bugs, allowing them to focus more on the feature development of the website. 👉 They'll move data to Storyblok from other content managment systems, ensuring a seamless transition. 👉 They coordinate content translation with third parties or AI for multilingual accuracy. 👉 Backend developers set up and maintain development and QA environments to prevent issues pre-launch. 👉 They work on middleware, like integrating with Salesforce and develop APIs crucial for Storyblok sites. This change is a positive step and opens up new opportunities for backend developers to enhance their skills and contribute more effectively to web development. This is not negative. It’s excellent. Do you agree? What’s your take on this?

21

8 Kommentare

SaaSbite (for software companies): Making them pay is NOT key. Making them stay is. The retention of new users who reached the AHA moment is ridiculously higher than those who don't. EVEN after they have paid already. Why? Because they "get" the product. Retention is about the value. And when they get it, they are willing to pay. (This picture is from Innertrends, for great product analytics)

3

Updating global JS is tricky business. The more functionality you run out of here, the more that can go wrong. There's a few things I can recommend: - Change control: It's really easy to have multiple people in here trying to tweak bits they need to, especially as the CRO team grows. The challenge is that snippet/script tag updates are normally not quick - someone will spend 30 mins debating whether or not it's tested enough to click Save. Having a point-person that's solely responsible takes away this problem. - QA/Testing: One of the cool things about Webtrends Optimize is that even our JS snippets/tags have a staging mode. There's also content overrides in devtools that do a great job, although minification means this isn't a 1:1 comparison. Knowing how far to QA is one of those "it's never enough" and "calculated risk" things though. - Documentation and notification: Telling people changes have been made is key. When something breaks, the most painful part of the process is often working out "what changed?". Being clear on what you did, when and why, in a way that people can look up easily is great. Webtrends Optimize comes with an audit trail that explains the "what", even if not the why. Github commit messages, a Slack channel - there are plenty of good places to leave a few notes about this. Including rollback options is always great. Even with all of this, things can go wrong. This doesn't necessarily protect you from every possible problem, but does at least make the knowledge more available and options for rolling back clear. Happy testing!

10

⭐ Build Websites like Legos: Why Component-Based Design is Winning The struggle is real with traditional page-based design. ♦️ The duplication of code across webpages costs wasted time & effort. ♦️ Updates become a nightmare – modifications are needed on multiple pages for the same component. ♦️ Maintaining a consistent look and feel? Really HARD to keep up as the website and team scales in size. 🔥 Forget building websites one static page at a time. As website development is expected to become more USER-CENTRIC and EFFICIENT, this calls for a flexible technical framework that can be more easily adaptable, scalable, and maintained. That’s where COMPONENT-BASED DESIGN comes in. In our newest article, we dived into: 👉 WHAT exactly is component-based design? 👉 HOW different is it from the page-based (page-by-page) design process? 👉 Does website development with component design vary across DIFFERENT TECH STACKS? 👉 KEY REASONS WHY component-based design is rising in popularity as the GO-TO DESIGN APPROACH for enterprises looking to scale and streamline their front-end web development. Find the FULL ARTICLE at: https://lnkd.in/et_4Y9as At IT Consultis (ITC), we specialize in empowering businesses with cutting-edge digital solutions tailored to their unique needs. From UX/UI design to bespoke local (Chinese) & global websites, Mini Programs, & apps development, we can help you bring your digital vision to life and establish the right technological foundation. Don’t hesitate to DM me for more information ;) #WebDevelopment #ComponentDesign #DigitalTransformation 

20

5 Kommentare

What a ride for Auctionata 👀 It's a tough reminder of how brutal the app market can be, especially for eCommerce. As an eCommerce software developer, I've seen firsthand how code errors can snowball as the app scales. #ecommerce #retail #webdevelopment #appdevelopment

17

11 Kommentare

A/B Test of the week # 1 This simple change got +$16,098/month for our client. Here’s what we did: 1. Identified collections that had manual sorting by default 2. Changed the default sorting to best selling Why did we do that? - It made sense to us to show products that generate the most revenue first - We saw that collections with best selling default sorting were performing better than others Result: Revenue Per Visitor increased by 21.3%. Here’s why we think it worked: - Visitors saw the products that they were most likely to buy first - It made the choice easier because the products with the most social proof (review stars) were first on the collection page Have you ever experimented with the default sorting on collection pages? Let me know! --- If you need help with finding big wins like this one on your website to increase profitability, DM me.

34

16 Kommentare

"People are spending less time searching and more time using LLMs like ChatGPT. So, how do you do SEO for LLMs?" Great question. In fact, people are spending more time on applications like ChatGPT, Gemini, Perplexity and Claude, and less time searching in Google. So, how do you make sure that your content appears on those answers produced by LLMs? It's not clear at all, but it's an exciting new world. It his Podcast episode, Nuno Morgadinho and I discuss this and other topics related to the AI and the future of the web. ▶ Watch it on youtube here: https://lnkd.in/dwxS2_Gk 🎧 If you would like to listen to it: Spotify https://lnkd.in/dfa4-tMx Apple Podcasts https://lnkd.in/dyc9f5sJ Amazon Music https://lnkd.in/dtykN_Cz #realAInow #podcast #artificialintelligence #generativeai #LargeLanguageModels

15

The shift is clear: traditional software houses will either evolve into #nocode agencies or be left behind. 💀 This may seem controversial, but let's take a deeper look! No-code platforms are taking the world by storm, and they're not just a passing fad. 🌊 Tools Bubble, Xano, WeWeb, Softr, Retool or Glide are not small startup companies but advanced software platforms that allow us to create really complex things. 🚀 Also, lots of Webflow agencies are looking into making apps, either by using Wized or learning how to build with Bubble. The fact is the more I am speaking with no-code agencies and seeing them grow exponentially the more I believe in a massive disruption in the tech industry. 📈 Let me give you some international examples like Kreante | NoCode&LowCode Agency, from zero to 25 developers and millions of dollars in revenue in 3 years 💰 or Creme Digital, from zero to revenues > $1M USD in 2 years 💸 Or some of the biggest Bubble agencies like Rapid Dev which hire over 50 developers and have over +200 projects 🚀 And all of this thanks to nocode! In Poland, where we have lots of software houses, this is just the beginning, but agencies like Davinci, havenocode, or Personit - Low-code Software Agency are taking over the industry with their no-code approach! 💥 On the other hand, many software houses are laying off people and struggling after years of growth. 😰 They cannot be competitive in the market anymore, where you can achieve similar effects with no-code: ⏱️ Speed to Market: Allowing businesses to bring their ideas to life in a fraction of the time compared to traditional coding methods. 🚀 🔁 Agility: Allowing to adapt quickly to changing market demands 🏎️ 📈 Scalability: No-code platforms are built for scalability - if you have doubts, check my latest interview with Maxime Topolov from code.store, where he explains how they are working on one of the most complex enterprise projects using low-code and no-code stacks. 🏢 So, what does this mean for traditional software houses? 🤔 In my opinion, they have two choices: 🌉 Embrace the no-code revolution by transforming themselves into no-code agencies. 🚀 🥇 Acquire or partner with existing no-code agencies, harnessing their expertise and staying ahead of the curve. 🤝 What are your thoughts on this? #TechTrends #SoftwareDevelopment #Innovation

94

66 Kommentare

Hello, #TYPO3 LinkedIn community. Lately, I've been mostly upgrading versions of TYPO3 CMS. Starting from versions TYPO3 6.x. There were even versions of TYPO3 4.x))) I found for myself the optimal order of steps to perform: Installing a new CMS TYPO3 12. I mainly use ddev and composer installation. Database Import. Correcting the database using SQL commands (if necessary). For this, I use a custom extension. Installation of new versions of extensions such as powermail or news, as well as custom extensions developed specifically for this project Database comparison. Execution of "Upgrade Wizard"  Transferring and correcting yaml, typoscript, tsconfig configurations.  Correction of templates. Fixing deprecated code. Please share, if you wish, how do you upgrade?

7

New homepage for Supercal.io is a huge upgrade compared to the previous. But it’s not over yet. I need to build comparisons pages with the alternatives. Plus case studies: how much time people are saving. This will come in due. First, I need to align on WHO I’m going after next. #supercal #buildinpublic

15

As I posted before, I see a direct correlation between the effectiveness of ratings and overall ASO performance. The question is: What is the best way to collect ratings and reviews? We have 2 ways: 1 - Ask openly during onboarding (more users, less precision) 2 - Ask after core feature usage (fewer users, higher precision) And today I learned about a 3rd way - ask after trial activation. Looks like a good balance between these two options. Super interesting to see how it will affect the ratings flow. Did you try this? What is your experience?

25

2 Kommentare

Google's SEO ranking algo and API data has leaked apparently, reveals over 14,000 ranking features. I did not get a chance to know the details of it. Anybody has any idea what's happening? Check it out here: https://lnkd.in/dEX8Ckp3 Thanks to iPullRank for analyzing. #googleSEOleak #googleSEO

4

POV: Most Shopify sites. ✨ Beautiful product pages on the frontend. VS 🔥 Full chaos on the backend. Way too many scripts and apps. All slowing down your site speed. Friday reminder for you: Your best CRO play may not be another extension. It's improving the speed of what you have. P.S. Join me and Nihar Kulkarni from ROSWELL this Weds for Shopify CRO tips powering 75+ stores with $250 million in GMV: https://hubs.ly/Q02C6s1d0

2.121

82 Kommentare

-Didn't you get the memo? - eeeeh? What memo? - The CoDeMeMo - Continuous Delivery Metric Model I'm excited and happy to re-publish the Continuous Delivery Model. This model originates from the time when I founded (2007) and operated Praqma. A company specialized in Continuous Delivery implementation of software development processes. Praqma is now gone. The company was swallowed in a merger and acquisition process in 2019 and the model didn’t survive. It was stored away in a GitHub repository and never used again. ...until now! The model was optimized specifically to be used as an assessment tool for helping companies to map their current Value Streams and to build a backlog for implementing Continuous Delivery. The assessment process was based on “The Toyota Way” principles: #ValueStreamMapping, #GenchiGenbutsu (observe deeply), identifying waste (#muda, #mura and #muri), measure #LeadTimes and Continuous Improvement (#kaizen) based on #5S (sort, straighten, shine, standardize, sustain). Lean Software Development! The assessment process we developed would span five intense workdays on-site, with a mix of all-hands-on-deck Value Stream Mappings, interviews, observations, and lean coffee workshops. Some of the larger assessments we did had 120 participants in the first-day Value Stream Mapping workshop. I’m now re-publishing the model. I had to rewrite the code as I didn't have acces to the original codebase. I enhanced readability and responsiveness, but more importantly I’ve turned the model into an open source template you can inherit from in #Jekyll and host it as a static web. Build your own model! ...More on that later! But for now I just want the release this MVP so we can get the model live again. How To Read The Model: Its a matrix with six different areas to consider in becoming black-belt Continuous Delivery - Software as a Factory champion. Each area has 5 levels of expertise ranging from novice to expert. Each card in the matrix represents a certain theme or disciplin. And each card is scored - by the team itself, during the workshops - for effect on three parameters: - Throughput (lead times) - Feedback (data for decision making) and - Payback (...on technical debt) And then scored for complexity as one of: - A low hanging fruit - A team effort - A mountain to climb To show-case the features of the model I have added an anonymized and generalized write-up of some of the typical or illustrative findings and mitigation from the total of 24 assessments that I conducted on the basis of this specific model. I've started out with the three first cards in the "Build" area - more will follow. You can subscribe to the atom feed in the footer on the website to get updates. I would love your feedback on the usefulness and suggestions for improvement. If you and you team would like to do this assessment on your product and process, I'm happy to announce that I'm back in business, charged and ready - just reach out!

38

18 Kommentare

For all the product companies running on Linear - I can highly recommend Productlane 👇 Building your product in public has been proven to lead to higher product adaption and more stickiness. #ProductDevelopment #Linear #BuildInPublic #Productlane #ProductManagement

22

1 Kommentar

Philipp Klöckner - Could you give us some insights into how your personal brand positively impacted your VC investment opportunities? Is it more important than SEO these days? ➡ 1) Aka running the Doppelgänger Tech Talk Podcast ➡ 2) Getting more people to know you ➡ 3) When someone needs VC money they'll talk to you. ➡ ... and start again with 1) For everyone else not knowing him - Philipp Klöckner and Philipp Gloeckler started the wonderful 🇩🇪 German language Doppelgänger Tech Talk Podcast a couple of years ago. Great tech topics. Great insights into companies trading on the public market. Highly recommended! #seo #personalbrand #socialmedia #podcast #vc

4

June 2024 Profit & Loss Report for Starlab Zone Decided to share these monthly statements for 2 reasons: 1. Full transparency in what it takes to build a software studio (focused on SaaS products). 2. Easy and thorough documentation of our progress. Context: - Super focused first 3 months of the year - Relocated to Dubai in April - Took a lengthy vacation - Experimented with content - Doubted the direction I chose, flip-flopped a bit - Last 2 weeks made the final decision to go all-in with Starlab - My time is not included as an expense Income: - Starlab Zone: $5,217.38 - Roast My SaaS: $225 (offered a 25% discount) - WorkSwift: $0 (pre-revenue) Total: $5,442.38 Expenses: - Stripe Fees: $244.91 - UX Engineer Freelancer: $1,100 - QA Engineer Freelancer: $280 - WorkSwift Hosting: $60 - Loom: $15 - Google Workspace: $36 - QuickBooks: $30 - DocuSign: $15 - Twitter: $8 Total: $1,788.91 Profit: $3,653.47 Margin: 67.13% Year-to-date revenue: $95,842.57. June was around 22% of the available capacity between the 3 of us and later when I'm going to replace myself, the profit margin will decrease further, but the amount of work we can handle will go up. Recently, I figured out a way to introduce product engineering by subscription. Normally, it doesn't work the same way as a design or marketing studio, but because we handle full-features (i.e. design, development, testing, release), there is a way that makes sense. But we haven't released this method yet. Funny thing is we don't even have a website: our work came through Upwork + referrals. Although I'm no longer active on the platform. Plan for July to increase revenue: 1. Do amazing work for existing clients. It's the most effortless way to make sure you don't lose what you've got going. 2. Publish teardowns of SaaS products. This is part of our content strategy to introduce prospects to our funnel. Here we first sell Roast My SaaS, then interested founders will be able to work with us as a product team. 3. Publish what I call "MVP Breakdowns" (will talk about this more in future posts). The other part of our content strategy for entrepreneurs that want to build a SaaS MVP. Each piece of content will direct to booking a call with me. 4. Boost content distribution with paid ads. We'll probably dedicate around $500 for this experiment because we're just getting started and don't want to flush money down the toilet. Let's see what July has in store for us. And if you want me to repeat this next month, please let me know in the comments! PS: Reposted because I forgot to include the image 🤦‍♂️ #buildinpublic

8

3 Kommentare

Input goals like number of calls made, signups, blog posts written are BAD. Output goals like revenue generated, activation rate, leads generated are GOOD. At least that’s been the zeitgeist in tech for the last decade. At best it’s naive . Yes, input goals can go wrong. Yes, you can end up doing a load of busy work that doesn’t move you forward. But output goals aren’t some miracle cure. They’re usually laggy and accountability is complex. If the initiative fails is it because of the execution or was the premise of the project wrong? Big results take big efforts. You need goals for execution AND impact. Inputs goals help motivate and keep you on track whilst you’re doing. Outputs ensure what you did had an impact. 

5

3 Kommentare