It depends entirely on the scope of your project: if your game involves viewing the entire terrain at all times with great quality then it might be better to have 1 single terrrain mesh. On the other hand if you require a big open world it usually is better to generate chunks. Then you can generate LODs and achieve a decent polycount without sacrificing quality/camera view distance.
That’s the main reason behind this project, it doesn’t provide LOD generation but the logic is there and you can easily extend it / use the provided methods:
@Glenn_Ko took it even further working on a quad tree terran LOD engine:
Again it depends on your project’s specs. If you are targetting a minimal app download size it is better to use heightmaps and generate the terrain on runtime. I don’t think there will be any visual difference between the devices as I feel all popular browsers will run the code with the same precision.
On the contrary if you are targetting low performant devices like mobile phones generating the terrain/chunks on runtime might put a lot of load on the CPU.