Will limited typed router functionality (compared to classic) be extended in future?

We investigate if it is possible for us to migrate from classic actors to typed actors. One obstacle is our usage of classic pool router SmallestMailboxPool with resizer DefaultOptimalSizeExploringResizer. We couldn’t find similar function for typed routers and we cannot implement it by our own, as actors are unable to determine either the mailbox size of their own mailbox nor the mailbox size of their children.

Do we have to stay on this classic router or is there an alternative?

While additional routing strategies may be added in the future it is very unlikely that the ones that peek into local mailboxes will be. I’d recommend staying with the classic APIs, they are not going away and can be mixed with typed APIs.