InfoComm Worldwide, LLC’s Post

https://lnkd.in/ePbWHT2G Covers one of the hardest challenges of all, designing an API that is both long-lived, that meets business objectives, and that your users will love. #GraphQLAPI #WebAPI #RestAPI #RestfulAPI #RestfulWebServices #WebServices

𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗮 𝗠𝗲𝘁𝗲𝗿𝗲𝗱 𝗨𝘀𝗮𝗴𝗲 𝗠𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴 𝗮𝗻𝗱 𝗔𝗹𝗲𝗿𝘁𝗶𝗻𝗴 𝗗𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱 𝘄𝗶𝘁𝗵 𝗡𝗲𝘅𝘁.𝗷𝘀 𝗮𝗻𝗱 𝗦𝗰𝗵𝗲𝗺𝗮𝘁𝗶𝗰 📊 We often get asked by our users if we can provide notifications for the customers that are approaching a limit in their products. Visibility into that type of information is incredibly useful, particularly for startups trying to identify their most active users or those ready for an upsell conversation. That said, it’s often challenging data both to get and to visualize in a user-friendly way that folks can act on. That’s because this type of data is often locked in application databases that need to be queried carefully & manually. Fortunately, Schematic supports metered features, and tracks data about limits and utilization on a per feature and per customer basis, which can be retrieved via our API. In this tutorial (link in comments), we'll build a small app that monitors feature usage across a customer base and triggers webhook notifications when customers are reaching usage limits. We'll use Next.js, Schematic's API to retrieve allocation and usage data for individual features, and webhook notifications for alerting.

Great post on map APIs based on your business need and budget.

"Honeycomb for Frontend Observability also captures detailed contextual event data, which developers can query for up to 60 days without pre-aggregation. This enables thorough investigations and hypothesis testing. The Query Assistant feature simplifies data analysis, making it accessible even to those without query language expertise." https://lnkd.in/ddfvRh57 #observability #frontend #honeycomb

Feedback from customers is one key to a successful business today. By building a customer review application, Temitope Oyedele shows you how to use Strapi as the backend and SolidJs, a JavaScript reactive framework, for building user interfaces. https://strp.cc/4bhPr3g

🕵️ The search is on! Navigating Kong Inc. Konnect just got more powerful with the revamped search bar! 🔍  Find the information you need across entities in Konnect, effortlessly, ✨in the UI, or using the Konnect Search API.  Meaning? - ☑️ Advanced query syntax caters to a wide range of your search requirements - 🔎 Search across vast numbers of entities easily and in less time - 📉 Intuitive, keyboard-friendly interface – minimal learning curve! Spend less time searching for the info you need and more time acting upon the results. #KongPin #APIs #Search #Konnect #APIManagement 

🕵️ The search is on! Navigating Kong Inc. Konnect just got more powerful with the revamped search bar! 🔍  Find the information you need across entities in Konnect, effortlessly, ✨in the UI, or using the Konnect Search API.  Meaning? - ☑️ Advanced query syntax caters to a wide range of your search requirements - 🔎 Search across vast numbers of entities easily and in less time - 📉 Intuitive, keyboard-friendly interface – minimal learning curve! Spend less time searching for the info you need and more time acting upon the results. #KongPin #APIs #Search #Konnect #APIManagement 

Real-Time Location Tracker with User Management This project is a real-time location tracking application that allows users to share and visualize their current locations on a map. Built with a focus on user interactivity, this application enables users to update their names, track distances traveled, and ping their current locations. The real-time updates are facilitated using WebSocket technology, ensuring seamless communication between clients and the server. The map is powered by the Leaflet library, which provides an intuitive interface for viewing user positions. Features Real-Time Location Sharing: Users can see each other’s locations in real-time. Distance Tracking: Calculates and displays the distance traveled by each user. User Name Management: Users can update their names, which are reflected on the map. Ping Location Button: Allows users to manually update and share their current location. Modal Interface: Easy-to-use modal for updating user information. Technologies Used Node.js: Backend server for handling WebSocket connections and HTTP requests. Express.js: Web framework for building the server-side application. Socket.IO: Library for real-time web applications, enabling bi-directional communication between clients and the server. Leaflet.js: JavaScript library for interactive maps, used to display user locations. EJS: Template engine for rendering HTML views. github: https://lnkd.in/dFyWVnDg

Part 1 (https://lnkd.in/dUYqBVvb) Now, let's take a closer look at the last point. We’ve created the filters, but where should we store their state? Local state, maybe Redux (or any other library you prefer), context, browser storage, or something else? Let’s think out loud. We’re okay with all the options, and we could make it simple and store it in local state. Now imagine this scenario: I, as a user, have a large amount of data, and I find the information I need on the page thanks to the filters I’ve set. Then something happens… I suddenly have to leave, close my computer, and the tab closes. When I return later, I realize I have to start all over again. What was there? What were the filters? Starting over isn’t fun. Now imagine how you could lose a customer over something small like this. Not good, right? So, we rule out local state right away. We can also eliminate storing data in Redux or context. Alright, let’s consider browser storage. Going back to the previous scenario. Here I am, a user, opening the page, setting the filters I need, and closing the page. I come back later, open it, and what do I see? Filters in place, data filtered. Cool? Well, let’s think. What if the user doesn’t need those filters anymore? But we’ve already filtered the data for them. Plus, constantly ensuring the data is up-to-date is not very convenient and can cause unexpected behavior. Or another scenario: I’m a user, working with a site containing corporate data. I filter the data, review it, and reload the page. The filters are still there. Great… but now I want to send this selection to my colleague to help them compile a report. I send them the link, they open it, and… it’s either blank or their own filters are applied… And now you’re annoyed by the site, because instead of sharing data in one click, you have to figure out what’s going on… And what if these two people, from the examples above, are business owners who pay to use your platform? Again, a potential customer lost over something minor. So, how can we solve this? (to be continue) Part 3 (https://lnkd.in/dvy_GZuZ)

This week we rolled out some cool new features inside Auditzy™ that further strengthen real time performance & core web vitals monitoring: 🚦Lighthouse v12.2 Integration We’ve updated our Synthetic (Lab Profile Based) Website Performance Tests to include Lighthouse v12.2. 🤩 Enhanced INP Data Accuracy We now provide more precise Interaction to Next Paint (INP) data across all user personas via Auditzy™ RUM. ✅ Streamlined Core Web Vitals Test & Comparison Our Core Web Vitals comparison feature now allows you to compare up to 5 URLs with just 6 clicks, down from the previous 14 clicks. 🚀 React Application Optimisation Despite having thousands of components, we reduced our React application bundle size by 15%. This was achieved through lazy loading and eliminating unused code. We aim to further reduce it by 25% in the coming months. If you're not familiar with Auditzy™, it’s a real-time website speed and performance monitoring tool designed to help you: 👉 Track Website Performance  👉 Real-Time Core Web Vitals Tracking 👉 Segmented Performance Insights 👉 Synthetic Performance Testing across 5000+ personas If you want to dive deeper into the nitty-gritty of what went live this week, our release notes link is in the comments 🔥