Not at all, there are two teams with differing skillsets here. The core functionality in routing and vaults has new members coming in to help. The other team works in getting the API’s available for application developers.
Our decision was to run these in parallel and provide the app devs the resources they require and at the same time allow the core vault code to get through the RFC’s and actually be able to test the client requirement as we go along. The current client API’s being introduced allow for instance messaging/chat/video conference etc. plus Wallets to be created as well as giving some great functionality to decentralised dynamic applications.
So there is cross over for certain, but all of this work really needs to happen to allow safecoin for 1 and a reason to use safecoin (beyond cash) secondly.
Hope that helps a bit. If something is not launch focussed then it’s just not done, but the client side should not stall for the vault side, they both must happen and developers need to get involved and build apps, even without vaults from home right now.
[Edit I should add disjoint groups is a huge part of work with three folk on it as will data chains be. After disjoint groups we have a smaller rfc (secure name/join) then data chains and in parallel probably vault start/reward]