Well this may not be entirely be related to UI, and it might involve some changes in code.
I think the UI should be fast,
Currently, what slows it down is the "Saved!" message.
When we press "Add Translation" button, it waits for the SQL query to finish before displaying "Saved!" and then going to next string.
Although, the time taken by SQL query to finish is not that much (~0.2s to 0.3s), but however the lag due to it is apparent.
So the best thing we can do is instead of waiting for SQL to finish, we can directly transfer the control to next string without waiting for the first one to complete. This will really speed the things up.
In case any error is there (unable to insert etc...), the user can be notified of it when it reaches the browser. Looks like you'll have to implement it asynchronously then, but i guess it'll be worth it.
Well this may not be entirely be related to UI, and it might involve some changes in code.
I think the UI should be fast, Currently, what slows it down is the "Saved!" message. When we press "Add Translation" button, it waits for the SQL query to finish before displaying "Saved!" and then going to next string.
Although, the time taken by SQL query to finish is not that much (~0.2s to 0.3s), but however the lag due to it is apparent.
So the best thing we can do is instead of waiting for SQL to finish, we can directly transfer the control to next string without waiting for the first one to complete. This will really speed the things up.
In case any error is there (unable to insert etc...), the user can be notified of it when it reaches the browser. Looks like you'll have to implement it asynchronously then, but i guess it'll be worth it.