According to the blog post in few months the managed workflow will get fully supported.
Just to make sure I got it right -
Is that basically means the end of the bare workflow??
This is extremely important to me as I planned on buying a MacBook in order to be able to eject and implement a library using native code.
Did I get it right? Should I wait couple of months for the managed workflow support implementation and see if it works for me?
Is that basically means the end of the bare workflow??
No, In EAS both workflows are starting to overlap a bit, but bare workflow will have still important use cases that managed workflow can’t handle. If the only reason for ejecting was adding some third party library then managed workflow on EAS will solve that but in most cases users will still need to use bare workflow.
in order to be able to eject and implement a library using native code.
Technically it would be possible, but EAS Build service is more intended to build app with native dependencies not to develop those native dependencies. You would need to wait 10-20 minutes for every native code change to check if your code even compiled. If you decide to do that I would suggest doing that in bare workflow, it would be a bit simpler this way and when you finish that library you can use it in managed project.