You shared the project as you promised in the previous article 😍 Really enjoyed seeing gp-grid put to use in an actual React project! STREET BITES is a great way to demonstrate how all these features come together in a realistic application. I especially like how you went beyond basic sorting and filtering to explore grouping, pivoting, inline editing, and virtual scrolling across different datasets.
The attention to details like custom cell renderers, dark mode, and responsiveness makes this a valuable showcase.
Software Engineer • Technical Writer (300K+ readers & 25K+ followers) • Trusted by 20+ startups and tech companies worldwide
I turn brands into websites people 💙 to use
Thank you so much! Really glad you enjoyed it! I wanted to go beyond testing individual features and see how they would work together in a real application. STREET BITES was a fun way to explore that, and I'm happy with how everything came together.
Founder & CEO, OBR Group. Leading innovation in business automation, AI, apps & financial systems. Empowering businesses to organize data & automate workflows with privacy-first digital ecosystems.
Education
Life has taught me a lot.
Pronouns
He/Him
Work
Founder & CEO, OBR Group. Leading innovation in AI, business automation & privacy-first systems.
Excellent work! 👏
What impressed me most about your project is that you didn't simply demonstrate individual features of gp-grid. You brought them together into a complete, practical React application.
Handling 10,000 vendor records, 5,000 dishes, and 72 events while integrating advanced filtering, sorting, inline editing, pivot tables, virtual scrolling, and live updates is a great example of thoughtful software engineering.
I particularly appreciate your use of virtual scrolling and your attention to usability, responsive design, and data organization. These are important considerations when building applications that handle large datasets.
Your STREET BITES project demonstrates how a powerful open-source library can be transformed into a useful and well-structured application.
As someone passionate about programming, algorithms, and software architecture, I genuinely appreciate the effort behind this implementation.
Congratulations on this excellent achievement, and thank you for sharing your experience and technical knowledge with the developer community! 👏
Software Engineer • Technical Writer (300K+ readers & 25K+ followers) • Trusted by 20+ startups and tech companies worldwide
I turn brands into websites people 💙 to use
That's what I wanted to achieve with this project: go beyond testing individual features and see how they work together in an actual application. I had a lot of fun building STREET BITES and exploring the different possibilities gp-grid offers along the way.
And yes, working with larger datasets while keeping the experience smooth and easy to navigate was an important part of the process.
Really glad you enjoyed the project and took the time to explore it.
I research AI tools, APIs & agents — comparing specs, pricing and real user reports — then publish honest rankings so you don't waste money. Research-first, never sponsored fluff.
The 10,000 vendors / 5,000 dishes / 72 events bit is what sold it for me — most grid demos use fifty rows and call it a day. Did the virtual scrolling hold up once you had inline editing and live updates running at the same time, or is that where it starts to creak? The food sections look great in the demo, by the way.
Software Engineer • Technical Writer (300K+ readers & 25K+ followers) • Trusted by 20+ startups and tech companies worldwide
I turn brands into websites people 💙 to use
That's actually a great question. I tested inline editing and live updates as part of the project, and both worked well alongside virtual scrolling. The grid recycles DOM slots as you scroll, so it doesn't need to render all the records at once. Inline edits also update the underlying application state, while live updates modify the relevant records and keep the surrounding UI in sync.
Of course, there's always more to test under heavier, real-world workloads, especially with frequent simultaneous updates. But I was happy with how gp-grid handled these scenarios in STREET BITES. That's one of the things I wanted to explore with this project: how these features behave together, not just individually.
Software Engineer • Technical Writer (300K+ readers & 25K+ followers) • Trusted by 20+ startups and tech companies worldwide
I turn brands into websites people 💙 to use
I agree that production behavior is where architectural decisions really prove their value. Keeping the critical runtime path understandable and avoiding unnecessary dependencies are both important, especially in applications handling large datasets.
That's also why I wanted to test gp-grid in a complete application, not just showcase its features in isolation. Of course, STREET BITES is a practical demo, not a substitute for testing under real production failures and workloads. There's still plenty to evaluate before making that kind of judgment.
The realistic scale is what makes this convincing — testing with 10,000 vendors, 5,000 dishes and 72 events instead of a 50-row demo shows where sorting, grouping and the pivot view actually start to matter. I also liked the Organizer mode idea: gating inline editing behind a toggle keeps the grids readable for visitors while still letting organisers fix a stall or a time directly in the table. Did the live-updates toggle ever surface a case where a stable getRowId mattered, like an event moving from Upcoming to Live while a visitor had it selected?
Software Engineer • Technical Writer (300K+ readers & 25K+ followers) • Trusted by 20+ startups and tech companies worldwide
I turn brands into websites people 💙 to use
Thank you! Really glad you picked up on those details! The Organizer mode was one of my favorite parts because I wanted editing to feel like a natural part of the application without making the visitor experience feel cluttered.
And yes, stable getRowId is definitely important in scenarios like this. When an event changes from Upcoming to Live, the grid needs a reliable way to identify that same record across updates. Without stable IDs, keeping row state, selection, and updates consistent can become tricky, especially when records are changing frequently.
I included getRowId in my practical tips for exactly that reason. It's a small implementation detail that can make a real difference as an application grows.
Building STREET BITES with gp-grid sounds like a great way to demonstrate how interactive food catalogs and vendor directories can improve the food festival experience.MenusBook restaurant menus cover thousands of chains and independents, giving you full item lists and prices in a single hub. Pick a restaurant and scan its menu before you decide where to eat.
Software Engineer • Technical Writer (300K+ readers & 25K+ followers) • Trusted by 20+ startups and tech companies worldwide
I turn brands into websites people 💙 to use
Thank you! 😍 I agree that having menus, prices, and food options easy to explore makes the whole experience much better for visitors. That's one of the reasons I chose a food festival for this project: it gave me a fun way to work with different types of data and put gp-grid's features into practice.
Checked out the live demo as well. The website looks really nice, especially the food sections! I also liked how you put gp-grid to use across the vendors, food explorer and schedule pages. Makes for a pretty cool project. 🍕👏
Software Engineer • Technical Writer (300K+ readers & 25K+ followers) • Trusted by 20+ startups and tech companies worldwide
I turn brands into websites people 💙 to use
Thank you so much for checking out the live demo! 😍 I'm really glad you liked the design! I had a lot of fun putting the different pages together and finding ways to use gp-grid for each type of data. The food sections were definitely fun to work on!
Really appreciate you taking the time to explore it! 💙
Software Engineer • Technical Writer (300K+ readers & 25K+ followers) • Trusted by 20+ startups and tech companies worldwide
I turn brands into websites people 💙 to use
nice try, but still not as good as the ag-grid... the scrolling in ag-grid is much better experience, no white spaces when the table is redrawn during scroll fast.
Software Engineer • Technical Writer (300K+ readers & 25K+ followers) • Trusted by 20+ startups and tech companies worldwide
I turn brands into websites people 💙 to use
AG Grid definitely has a mature scrolling experience. However, I think gp-grid deserves credit for what it already offers, especially as an open-source library with all its advanced features available under the Apache 2.0 license, without paid feature restrictions.
The goal of my project was to explore its capabilities in a real React application, and I was genuinely impressed by how much I could build with it. Of course, there's still room for improvement, including scrolling performance, but that's also part of what makes testing and contributing to growing open-source projects interesting.
AG Grid is a strong option, but I wouldn't dismiss gp-grid based on one area that still needs polishing. It has a lot of potential!
We're a place where coders share, stay up-to-date and grow their careers.
You shared the project as you promised in the previous article 😍 Really enjoyed seeing gp-grid put to use in an actual React project! STREET BITES is a great way to demonstrate how all these features come together in a realistic application. I especially like how you went beyond basic sorting and filtering to explore grouping, pivoting, inline editing, and virtual scrolling across different datasets.
The attention to details like custom cell renderers, dark mode, and responsiveness makes this a valuable showcase.
Thank you so much! Really glad you enjoyed it! I wanted to go beyond testing individual features and see how they would work together in a real application. STREET BITES was a fun way to explore that, and I'm happy with how everything came together.
Excellent work! 👏
What impressed me most about your project is that you didn't simply demonstrate individual features of gp-grid. You brought them together into a complete, practical React application.
Handling 10,000 vendor records, 5,000 dishes, and 72 events while integrating advanced filtering, sorting, inline editing, pivot tables, virtual scrolling, and live updates is a great example of thoughtful software engineering.
I particularly appreciate your use of virtual scrolling and your attention to usability, responsive design, and data organization. These are important considerations when building applications that handle large datasets.
Your STREET BITES project demonstrates how a powerful open-source library can be transformed into a useful and well-structured application.
As someone passionate about programming, algorithms, and software architecture, I genuinely appreciate the effort behind this implementation.
Congratulations on this excellent achievement, and thank you for sharing your experience and technical knowledge with the developer community! 👏
Thank you so much! 😍
That's what I wanted to achieve with this project: go beyond testing individual features and see how they work together in an actual application. I had a lot of fun building STREET BITES and exploring the different possibilities gp-grid offers along the way.
And yes, working with larger datasets while keeping the experience smooth and easy to navigate was an important part of the process.
Really glad you enjoyed the project and took the time to explore it.
The 10,000 vendors / 5,000 dishes / 72 events bit is what sold it for me — most grid demos use fifty rows and call it a day. Did the virtual scrolling hold up once you had inline editing and live updates running at the same time, or is that where it starts to creak? The food sections look great in the demo, by the way.
Thank you! Glad you liked the food sections! 😄
That's actually a great question. I tested inline editing and live updates as part of the project, and both worked well alongside virtual scrolling. The grid recycles DOM slots as you scroll, so it doesn't need to render all the records at once. Inline edits also update the underlying application state, while live updates modify the relevant records and keep the surrounding UI in sync.
Of course, there's always more to test under heavier, real-world workloads, especially with frequent simultaneous updates. But I was happy with how gp-grid handled these scenarios in STREET BITES. That's one of the things I wanted to explore with this project: how these features behave together, not just individually.
Clean architecture is easy to maintain in a slide deck; the real test is how gracefully the system degrades under cascading production failures.
Minimizing abstraction layers and owning your critical runtime path will always outperform adding more third-party glue.
I agree that production behavior is where architectural decisions really prove their value. Keeping the critical runtime path understandable and avoiding unnecessary dependencies are both important, especially in applications handling large datasets.
That's also why I wanted to test gp-grid in a complete application, not just showcase its features in isolation. Of course, STREET BITES is a practical demo, not a substitute for testing under real production failures and workloads. There's still plenty to evaluate before making that kind of judgment.
The realistic scale is what makes this convincing — testing with 10,000 vendors, 5,000 dishes and 72 events instead of a 50-row demo shows where sorting, grouping and the pivot view actually start to matter. I also liked the Organizer mode idea: gating inline editing behind a toggle keeps the grids readable for visitors while still letting organisers fix a stall or a time directly in the table. Did the live-updates toggle ever surface a case where a stable getRowId mattered, like an event moving from Upcoming to Live while a visitor had it selected?
Thank you! Really glad you picked up on those details! The Organizer mode was one of my favorite parts because I wanted editing to feel like a natural part of the application without making the visitor experience feel cluttered.
And yes, stable
getRowIdis definitely important in scenarios like this. When an event changes from Upcoming to Live, the grid needs a reliable way to identify that same record across updates. Without stable IDs, keeping row state, selection, and updates consistent can become tricky, especially when records are changing frequently.I included
getRowIdin my practical tips for exactly that reason. It's a small implementation detail that can make a real difference as an application grows.Building STREET BITES with gp-grid sounds like a great way to demonstrate how interactive food catalogs and vendor directories can improve the food festival experience.MenusBook restaurant menus cover thousands of chains and independents, giving you full item lists and prices in a single hub. Pick a restaurant and scan its menu before you decide where to eat.
Thank you! 😍 I agree that having menus, prices, and food options easy to explore makes the whole experience much better for visitors. That's one of the reasons I chose a food festival for this project: it gave me a fun way to work with different types of data and put gp-grid's features into practice.
Checked out the live demo as well. The website looks really nice, especially the food sections! I also liked how you put gp-grid to use across the vendors, food explorer and schedule pages. Makes for a pretty cool project. 🍕👏
Thank you so much for checking out the live demo! 😍 I'm really glad you liked the design! I had a lot of fun putting the different pages together and finding ways to use gp-grid for each type of data. The food sections were definitely fun to work on!
Really appreciate you taking the time to explore it! 💙
I loved the app 😍
Glad you liked it 😍
nice try, but still not as good as the ag-grid... the scrolling in ag-grid is much better experience, no white spaces when the table is redrawn during scroll fast.
AG Grid definitely has a mature scrolling experience. However, I think gp-grid deserves credit for what it already offers, especially as an open-source library with all its advanced features available under the Apache 2.0 license, without paid feature restrictions.
The goal of my project was to explore its capabilities in a real React application, and I was genuinely impressed by how much I could build with it. Of course, there's still room for improvement, including scrolling performance, but that's also part of what makes testing and contributing to growing open-source projects interesting.
AG Grid is a strong option, but I wouldn't dismiss gp-grid based on one area that still needs polishing. It has a lot of potential!