How to make a user friendly software product
0 likes38 views
Jalan Technology Consulting emphasizes the importance of user-friendly software by addressing the balance between customer and user needs in B2B software. They advocate for proactive monitoring systems to ensure software usability, utilizing alerts for system performance and error handling. The firm collaborates with entrepreneurs to develop software products, inviting partnerships for technological assistance.
How to make a user friendly software product
- 1. Jalan Technology Consulting //01 How to Make a User Friendly Software Product?
- 2. Jalan Technology Consulting //02 “Usability” of a software product refers to the ease of use of a product or website The apparent conflict between customer needs and user needs in B2B or Internal software can be annoying. Good software is one that responds to requests as quickly as possible.
- 3. Jalan Technology Consulting //03 Over the years, one of the questions that the business team often ask after release - "how do we know everything is working as expected"?
- 4. Jalan Technology Consulting //04 It's not about the product - whether it was built was right or wrong. This is about whatever you shipped - are your users able to use it or not and how can you know it proactively before your user tells you about it.
- 5. Jalan Technology Consulting //05 Team Required for Software Monitoring.
- 6. Jalan Technology Consulting //06 Your operation team is solely responsible for monitoring, but recently the shift has been toward cross-discipline engineers who build, test, monitor, and are on call for their applications. These cross-discipline engineers are sometimes called DevOps engineers or site reliability engineers (SREs).
- 7. Jalan Technology Consulting //07 How to Identify your Software's Usability?
- 8. Jalan Technology Consulting //08 From an engineering standpoint, following are some key metrics that your team should track to monitor the system.
- 9. Jalan Technology Consulting //09 For Backend System should send an alert to engineering team (Slack channel, email etc.) whenever the main process crashes.
- 10. Jalan Technology Consulting //10 System should restart the service whenever the main process crashes.
- 11. Jalan Technology Consulting //11 System should send an alert to engineering team (Slack channel, email etc.) whenever an unhandled exception is raised
- 12. Jalan Technology Consulting //12 System should send an alert to engineering team (Slack channel, email etc.) whenever error or warning level logs are logged by the application. This is important - please make sure you do correct logging in your application during development.
- 13. Jalan Technology Consulting //13 The system should send an alert to the engineering team (Slack channel, email, etc.) whenever the machine is running over 90% utilization (memory or CPU)
- 14. Jalan Technology Consulting //14 System should log a warning message whenever a key application operation takes more than n seconds. This should be determined with the product team during development.
- 15. Jalan Technology Consulting //15 If the backend exposes API (REST or Graphql), the system should send an alert to engineering team (Slack channel, email etc.) whenever an API response takes more than n seconds.
- 16. Jalan Technology Consulting //16 For Frontend (typically React or React Native) System should send an alert to engineering team (Slack channel, email etc.) whenever unhandled JS exception is thrown
- 17. Jalan Technology Consulting //17 System should log a warning if time to render a screen (i.e. the screen is usable by the user) if it takes more than n seconds.
- 18. Jalan Technology Consulting //18 We work with entrepreneurs and business leaders to execute their vision by building software products. If you are looking for a technology partner, feel free to reach out to jjalan@jalantechnologies.com. We hope our assistance will help. Thank You!