This question keeps popping up now and then.
Wireless roaming is purely a client related matter. Your smartphone or laptop will be the device that decides if it's going to move to a new (now stronger/closer) AP or not. This is standard WiFi functionality and keeps getting improved each WiFi version. This can however cause a slight hiccup when it moves over from one AP to another, but on a properly configured system, this should be almost impossible to notice (missing maybe 1 ping, if any).
Backstory, what is often referred to is known as "true seamless roaming" and it's a very special setup where all the access-points are run on the same frequency and sending out the same ID and a central controller takes all the packets in from those and makes sure everything works correctly. That way, the client never knows which AP it's sending its data to and thus it's supposed to be completely seamless (in theory). There are however a lot of downsides with this kind of setup. It's very much out of RFC specs so it has a lot of compatibility issues, all AP's are run on the same channel limiting the available bandwidth severely, using multiple chains is an issue (limiting bandwidth even further), newer features such as AC or mu-mimo are NOT going to work, and well, the list keeps going.
Only when you have a VERY specific use case (For instance, you have a large warehouse and a few (not too many because the system will become overloaded because of shared bandwidth) wireless scanners which for some reason cannot roaming themselves (bad hardware/software), this could work, but better to replace the scanners then design some kind of weird wireless system.
So, the proper way to set it up and have as little as possible roaming hiccups is by running a Mikrotik CAPsMAN setup and running all traffic tunneled to a central router. That way when a client roams it will keep it's DHCP assignment and sessions so it basically won't notice a thing when changing between AP's.
As an example, I have 5 AP's setup in my own home (5x wAP AC) with a CCR1009 as my main router which runs CAPsMAN. All traffic comes in from whatever AP I'm connected to and even when downloading and running around the house and grounds, I always stay connected and something like a download keeps running without an issue. CAPsMAN in the logs clearly shows I'm hopping between AP's but all sessions stay alive without issue.
I've included what the central CAPsMAN router shows in the logs and where you can see how my phone connects to whatever AP is best at that time.
capsmanroaming.png
So I believe the setup you are looking for can work perfectly well for your intended application! RB4011 itself is also powerful enough to be used as a central router and CAPsMAN head.
p.s. I know the discussion in that topic highlights missing features such a 802.11r and 802.11k support and although they might provide some form of benefit, in my home situation with between 20 to 50 devices I don't seem to miss it much.
You do not have the required permissions to view the files attached to this post.