Empowering the End User to be More Sustainable in Web Applications
summary
Claims that letting users choose profiles for update frequency and hide unused panels cuts server and client work (example: updates per second vs once per minute). Implements a small plug UI called Leaf and a Java framework using declarative annotations, centralized configs and a dynamic proxy to toggle features at runtime. Uses estimated energy cost (not live measurement), reports high user acceptance in a study, reduces developer conditional complexity, and plans a front-end API for wider integration.
AI-written summary · about
chapters (7)
- 0:00Introduction to sustainability
- 2:09User powerlessness in web apps
- 5:29Introducing the Leaf solution
- 8:40User acceptance study results
- 10:49Technical framework details
- 12:35Future plans and API integration
- 13:18Q&A on energy estimation
related talks
49mThe Future is 💚: A Journey through the Energy Efficient ..
47mHow to develop a frontend approach to eco-design: Soft Disabling
47mDigitalize the Society — Sustainable or Die
31mCreate an eco-friendly world with Green Software Engineering
39mCreate an Eco-Friendly World with Green Software Engineering
25mPanel
38mSustainable Web Design: Principles and Best Practices
28mDynamic UI at the Edge