Improve how your #Vaadin app handles long backend actions. From showing progress indicators to async processes, Matti Tahvonen shares the best ways to keep users engaged. Check out the demo! 🔗 Dive in: https://bit.ly/4dwwcnx
Vaadin’s Post
More Relevant Posts
-
✅ Just Released: A Simple TODO List App using Redux Toolkit! In this project, I used the Redux Toolkit to manage the state of a TODO list application. This toolkit simplifies working with Redux, making state management more efficient and developer-friendly. Why it's cool: Streamlined state management with Redux Toolkit. Intuitive UI for task management. Code available here: [https://lnkd.in/gzsDwbc4] #React #ReduxToolkit #TODOList #WebDevelopment
To view or add a comment, sign in
-
🚀 Just Launched: My Simple Recipe App! 🍽️ Excited to share that I've built a straightforward recipe app that fetches data dynamically from an API and includes basic routing for seamless navigation. It’s a minimalist project focused on functionality and user experience. 🔗 Features: API integration for real-time recipe data. Clean and intuitive UI with easy navigation. Basic routing to enhance user interaction. I’m continually learning and improving, and this project is another step forward in my journey as a developer. Check it out and let me know your thoughts! Here is demo☺️ https://lnkd.in/dXA2Z7P3 Here is code ☺️ https://lnkd.in/dRnsjxgV #React #API #WebDevelopment #LearningByDoing #MERNStack
To view or add a comment, sign in
-
🚀 ज्ञा.jnaa - Astra: Build Apps at Lightning Speed! • Federated, Container-Native App Builder • 📝 Todo App in 2 Minutes (Preview Mode + Hot Reloading) • 🌐 Deployed at todo-app.preview.jnaa.tech • 🔥 Added Header Feature in real-time ✨ Future of Composable UI Containers? Explore: jnaa.tech
To view or add a comment, sign in
-
Breaking boundaries with custom pages for intuitive Power Apps model-driven UI by Kimmo Koski at CollabDays Finland 😺 Rember the history of model-driven apps and the elements of ribbon and form - customized solutions were about various client and sever side hacks 😸 Power Platform changed the game with native components and thought of one UI - the custom page combining Canvas App and Model-Driven App 😿 Embedded Canvas App can be used in forms but they don't live in the context, when Custom Page does not go inside forms 😹 Low-code developers don't want to use Javascript to open custom pages in dialog - there's no option for it 😭 😻 There is possibility to open in side pane which does not close when user continues navigation in Model-Driven app 😼 Override record view in page is one easy choice when you ding want to open separate dialogs 😽 Then a lot of 🙀 great demos 😾 #microsoft #modeldrivenapp #powerplatform #powerapps #custompage #ui
To view or add a comment, sign in
-
Weather app (2/2024) It is a very simple UI application, but it depends on the API It is built on a clean code approach
To view or add a comment, sign in
-
🧩 Composing Components Together React allows components to contain other components, building complex UIs from simple pieces. 👉 const App = () => { return ( <div> <Header /> <Content /> <Footer /> </div> ); } 👈 By composing components, you can create intuitive, scalable user interfaces!
To view or add a comment, sign in
-
🚀 𝐌𝐚𝐬𝐭𝐞𝐫 𝐭𝐡𝐞 𝐀𝐫𝐭 𝐨𝐟 𝐂𝐮𝐬𝐭𝐨𝐦 𝐄𝐫𝐫𝐨𝐫 𝐒𝐜𝐫𝐞𝐞𝐧𝐬 𝐢𝐧 𝐎𝐮𝐭𝐒𝐲𝐬𝐭𝐞𝐦𝐬 Customizing error screens is crucial for delivering a smooth user experience, and our OutSystems front-end expert, Paulo Solipa has just published the first part of an insightful series on how to do it like a pro. In Part 1, learn how to customize your error screen through OutSystems Extensibility Configurations and take your app's error handling to the next level. Don't miss out on these expert tips to enhance your app's look and feel! 📖 Read the full article here: https://lnkd.in/g4tpstYU #OutSystems #AppDevelopment #ErrorHandling #Customization #TechTips #OutSystemspartner #frontend
To view or add a comment, sign in
-
Recently, I looked into some tools for making a whiteboard app and found two interesting options: - Excalidraw: It comes with a ready-made UI and tools, so it’s really easy to get started. - React Flow: This one’s more of a plugin system, so you can customize pretty much everything. I went with React Flow since it lets me control all the details. To try it out, I built a project over the weekend called Flowcode. Flowcode is a simple whiteboard app where you can drag and drop to make basic flowcharts. In the future, I might add a feature that turns these flowcharts into code. Until then, feel free to check it out here: 🎉 https://lnkd.in/gGbjFcv9
To view or add a comment, sign in
-
𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 𝘁𝗵𝗲 𝗔𝗰𝘁𝗶𝘃𝗶𝘁𝘆 & 𝗙𝗿𝗮𝗴𝗺𝗲𝗻𝘁 𝗟𝗶𝗳𝗲𝗰𝘆𝗰𝗹𝗲 𝗶𝗻 𝗔𝗻𝗱𝗿𝗼𝗶𝗱 The Activity and Fragment Lifecycle are fundamental concepts in Android Development. They define how these building blocks of your app behave throughout their lifecycle (creation, pausing, resuming, destruction). i). An Activity represents a single screen within your app. ii). Fragments are modular components that can be used within activities to build your app's UI. Both Activities and Fragments go through different states during their lifecycle. Understanding these states is crucial for writing clean and efficient code. Here's a simplified breakdown: 𝗔𝗰𝘁𝗶𝘃𝗶𝘁𝘆 𝗟𝗶𝗳𝗲𝗰𝘆𝗰𝗹𝗲: onCreate() -> onStart() -> onResume() -> onPause() -> onStop() -> onDestroy() 𝗙𝗿𝗮𝗴𝗺𝗲𝗻𝘁 𝗟𝗶𝗳𝗲𝗰𝘆𝗰𝗹𝗲: onAttach() -> onCreate() -> onCreateView() -> onActivityCreated() -> onStart() -> onResume() -> onPause() -> onStop() -> onDestroyView() -> onDestroy() -> onDetach() 𝗧𝗵𝗶𝘀 𝗶𝘀 𝗮 𝘃𝗲𝗿𝘆 𝗵𝗶𝗴𝗵-𝗹𝗲𝘃𝗲𝗹 𝗼𝘃𝗲𝗿𝘃𝗶𝗲𝘄. 𝗜'𝗹𝗹 𝗯𝗲 𝘀𝗵𝗮𝗿𝗶𝗻𝗴 𝗺𝗼𝗿𝗲 𝗱𝗲𝘁𝗮𝗶𝗹𝗲𝗱 𝗶𝗻𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝗼𝗻 𝗼𝗻 𝗔𝗰𝘁𝗶𝘃𝗶𝘁𝗶𝗲𝘀 𝗮𝗻𝗱 𝗙𝗿𝗮𝗴𝗺𝗲𝗻𝘁𝘀 𝗶𝗻 𝘁𝗵𝗲 𝗰𝗼𝗺𝗶𝗻𝗴 𝗱𝗮𝘆𝘀.
To view or add a comment, sign in
-
This is the no. 1 way to save more time. (And it takes less than 10 minutes). Everyone can build a React web app, most use "forever" to finish. Why? Because they build apps without making components reusable. Here's how I create reusable components (step-by-step): 1. Identify repetitive patterns in your app. 2. Create a new component for 1 purpose. 3. Name it descriptively (e.g. FormInput, Card). 4. Copy the JSX that you want to make reusable. 5. Create the props value, pass it as an argument. 6. Use the props to customize components behavior. 7. Export your components → reuse when you need to. STOP reinventing the wheel for every feature. SAVE yourself more time by making your components reusable. See how I created a "basic" reusable component in the comments. P.S. Do you create reusable components this way too?
To view or add a comment, sign in
11,922 followers