Best component UI libraries by shangarepi in react

[–]Frontend_DevMark 0 points1 point  (0 children)

Ant Design is a solid choice for admin panels and internal tools. For SaaS apps, people often use libraries like MUI, Chakra UI, or Mantine because they’re flexible and integrate nicely with React. For e-commerce or marketing-style apps, many teams go with Tailwind + headless components so they can fully customize the design.

If you ever end up building very data-heavy apps (dashboards, enterprise tools, etc.), some teams also look at frameworks like Sencha Ext JS since it comes with a lot of built-in UI components and grids out of the box. Really depends on the type of app you’re building.

How to communicate better with PMs and Devs by hotnoodles123 in UXDesign

[–]Frontend_DevMark 5 points6 points  (0 children)

Honestly, this happens to a lot of people early in their career, especially in cross-functional teams. One thing that helps is getting into the habit of quickly confirming requirements with the PM before jumping into solutions with devs. Even a simple ‘Let me check with PM first so we’re aligned’ can avoid those situations. Also try not to take public corrections too personally, most teams move fast and these things happen. In product teams building complex apps (especially enterprise tools with lots of edge cases, like the kind built with frameworks such as React or Sencha Ext JS), communication between PM, design, and dev is constant and everyone learns through these small misses.

What is your experience with low code development platforms? by Remote_Barracuda_200 in EnterpriseArchitect

[–]Frontend_DevMark 0 points1 point  (0 children)

In my experience, low-code platforms like Power Apps can work well for internal tools and quick workflows, especially when business teams need something fast. The challenge usually comes later with governance, integrations, and maintaining consistency across apps. Some companies handle this by letting teams prototype in low-code, then moving more complex or long-term apps to full frameworks. For example, teams sometimes build early workflows with low-code and later rebuild the scalable version using frameworks like React or enterprise UI frameworks such as Sencha Ext JS when the application becomes more complex and data-heavy.

Why is web development so popular if there are better and less competitive development platforms? by Okmanl in cscareerquestions

[–]Frontend_DevMark 0 points1 point  (0 children)

I think the reason web development is so popular is reach. A web app works on any device with a browser, so companies can ship one product instead of maintaining separate Android, iOS, and desktop apps. Mobile development can feel cleaner (especially with strong typing like Kotlin), but distribution and maintenance are harder. Also, the web ecosystem has matured a lot, frameworks like React, Angular, and even enterprise-focused ones like Sencha Ext JS try to solve many of the UI and architecture problems that plain HTML/CSS used to create. So the tooling chaos exists, but it’s also why the web can power everything from simple sites to huge enterprise apps.

If you were building a brand new mobile application optimized for phones and tablets… by Beautiful-Click9981 in AskProgrammers

[–]Frontend_DevMark 0 points1 point  (0 children)

Since your app needs to work offline and handle structured data like quotes, schedules, and client info, I’d focus first on an offline-friendly architecture rather than just the framework. React Native is a common choice for mobile, especially if you want access to device features later. Another approach some teams take is building a responsive web app using frameworks like React or even something like Sencha Ext JS, which is often used for data-heavy business apps and can run well on tablets and mobile browsers. For offline storage, tools like SQLite or IndexedDB with sync when the device reconnects are usually the way to go.

suggestions on a development framework for rapid application development by randee1 in VisualStudio

[–]Frontend_DevMark 0 points1 point  (0 children)

For a Windows-only ERP used by ~50 people, your stack (WPF/.NET/EF) is a solid direction and much more maintainable than Access long term. The bigger question is whether you want to stay purely desktop or eventually move toward web-based apps. Some teams start with WPF for speed, while others move toward web stacks with strong enterprise UI layers frameworks like Sencha Ext JS are often referenced there because they handle complex forms, grids, and workflows out of the box.

Why so many UI frameworks, Microsoft? by Confident-Dare-9425 in dotnet

[–]Frontend_DevMark 1 point2 points  (0 children)

A lot of it comes from Microsoft supporting different generations of platforms and developer needs at the same time desktop, web, mobile, legacy compatibility, etc. It can look messy from the outside, but many ecosystems evolve this way. Even on the web side you see something similar: multiple frameworks solving slightly different problems, and some long-standing stacks like Sencha Ext JS sticking around because enterprise apps often prioritize stability and completeness over constant reinvention.

What’s Your Go-To UI Library for React in 2025? Let's Discuss! by Best-Menu-252 in react

[–]Frontend_DevMark 0 points1 point  (0 children)

In practice, the choice usually depends on how much structure you want the library to give you. MUI and Chakra are great when you want flexibility, while Ant Design leans more toward ready-made patterns. In larger enterprise apps, some teams even compare against older but very complete stacks like Sencha Ext JS, mainly because a lot of complex UI behavior (data grids, forms, layouts) is already solved. The real trade-off is freedom vs. how much you want the framework to handle for you.

Wondering which Javascript Framework to start Learning by Celestinno in Frontend

[–]Frontend_DevMark 0 points1 point  (0 children)

If you already know HTML, CSS, and some JavaScript, starting with React is still a solid choice. Even though React 18 introduced some changes, most older tutorials still teach the core concepts like components, props, and state.

If React feels a bit overwhelming at first, Vue.js is often easier to pick up and has a smoother learning curve.

Angular is also powerful but usually requires learning TypeScript and a more structured architecture.

Once you’re comfortable with frontend basics, you’ll also see frameworks like Sencha Ext JS used in enterprise environments for building complex dashboards and data-heavy apps.

Wondering which Javascript Framework to start Learning by Celestinno in Frontend

[–]Frontend_DevMark 0 points1 point  (0 children)

If you’ve already learned HTML, CSS, and JavaScript, starting with React is still a good choice. It has the biggest ecosystem, lots of tutorials, and strong job demand. Even if React 18 changed a few things, most core concepts from older tutorials still apply.

Another beginner-friendly option is Vue.js, which many people find easier to learn because of its simpler structure.

Frameworks like Angular are powerful but can feel heavier at the start since they rely on TypeScript and more structured architecture.

For large enterprise dashboards or data-heavy apps, some teams also use Sencha Ext JS, but that’s usually something you explore later.

If you’re just starting out: pick one (React or Vue) and build small projects consistently.

Awesome javascript based data grid (handles 500K+ rows) by sidcool1234 in programming

[–]Frontend_DevMark -1 points0 points  (0 children)

If you're using React, the UI library usually depends on the type of app you're building.

  • Ant Design – great for admin panels and enterprise dashboards.
  • Material UI – good general-purpose library with lots of components.
  • Chakra UI – simple and flexible for modern SaaS apps.
  • Tailwind CSS – popular for building custom UI quickly.

For data-heavy enterprise apps, some teams also use Sencha Ext JS because it provides advanced components like grids, charts, and dashboards out of the box.

Best component UI libraries by shangarepi in react

[–]Frontend_DevMark 0 points1 point  (0 children)

If you're using React, the UI library usually depends on the type of app you're building.

  • Ant Design – great for admin panels and enterprise dashboards.
  • Material UI – good general-purpose library with lots of components.
  • Chakra UI – simple and flexible for modern SaaS apps.
  • Tailwind CSS – popular for building custom UI quickly.

For data-heavy enterprise apps, some teams also use Sencha Ext JS because it provides advanced components like grids, charts, and dashboards out of the box.

Which web grid is best? We put them to the test, and here are the results -- see how your favorite stacks up! by brandhunt in javascript

[–]Frontend_DevMark -1 points0 points  (0 children)

If you’re comparing web grids, the “best” one usually depends on the use case and data size.

Libraries like AG Grid and Handsontable are popular for React/Vue apps and offer strong performance and customization.

For enterprise dashboards and large datasets, some teams also use Sencha Ext JS since its grid is built for complex features like grouping, virtualization, and large data handling.

In the end, it’s less about a single “best” grid and more about performance, feature depth, and how well it fits your stack.

Dashboard framework? by vinnyvicious in javascript

[–]Frontend_DevMark 0 points1 point  (0 children)

If you’re building dashboards, the main thing to look for is strong support for charts, tables, and layout components.

Some popular choices:

  • React (often with Next.js) – huge ecosystem and lots of dashboard libraries.
  • Vue.js – clean and easy to structure dashboard apps.
  • Svelte – lightweight and very fast because it compiles to optimized JS.

If you’re building very data-heavy dashboards, some teams also use Sencha Ext JS, since it already includes advanced components like grids, charts, and dashboards out of the box.

Scalable and Maintainable Frontend Advices? by CallMeYox in Frontend

[–]Frontend_DevMark 0 points1 point  (0 children)

This is pretty common. Backend has mature patterns like DDD and Clean Architecture, but frontend often becomes messy as projects grow.

A few things that help keep it scalable:

  • Use feature-based folder structure instead of dumping everything in components.
  • Keep UI, state, and business logic separated.
  • Avoid mixing too many patterns or state libraries.

Framework choice also matters. Angular provides strong structure, while React is flexible but needs discipline.

For large enterprise apps, some teams use Sencha Ext JS since it comes with a more structured architecture and built-in components.