Coffee is not a good excuse for a slow application start-up time. Should it be fixed? Ideally yes. But in the real world, it depends. Is the user billed hourl

Coffee is not a good excuse for a slow application start-up time. Should it be fixed? Ideally yes. But in the real world, it depends. Is the user billed hourly (and therefore do they want you to fix it)? What's the business context? Will it help other users? (Are there other users?) What is the app doing in those 8 minutes and how would reducing it affect (positively or negatively) the user experience after startup? Yes, getting a faster start time is ideal, but assuming limited resources you need to figure out what the biggest user experience problems are and fix those first. If you application takes 8 minutes to load, the biggest user problem may well exist AFTER the application has loaded. Fix that first.