@f-odhiambo @jingtang10

What if instead of handling changed input every time text is changed we handle input only when user stops writing ?
Technically,

if (lastEditTime - currentTime > THRESHOLD_TIME) 
    handleInput(editable!!, questionnaireViewItem)
lastEditTime = currentTime

@MJ1998 yeah that could work well for edit text.
But we also have lags for selection type input.

What I did so far:

1. Limiting the calculation for calculatedExpression to the current page, yes there are less calculation but the lags is still there.
2. Move the execution of getQuestionnairePages, which takes approximately 2 seconds, to a background thread. By doing so, any potential lags in selecting or typing an answer can be avoided. However, it is important to prevent the user from navigating to the next page prematurely, as the subsequent page could be a blank page due to the ongoing getQuestionnairePages process. Hence, the 'Next' button should remain disabled until the 2-second process concludes. The user will only notice the disabled 'Next' button if the process takes a considerable amount of time, as demonstrated here. For simple questionnaires, users are unlikely to notice the disabled next button i.e. will immediately see it as enabled.

@shelaghm let me know if you're ok w this.
I'm showing a circular progress indicator on a button, instead of disabling the button, to indicate a background process that the app needs to complete.

https://m3.material.io/components/progress-indicators/guidelines#83ca07cc-3731-4e1b-a865-ba11dc5bd00c

@FikriMilano is working on this