If something can be done(created) with code it will end up done with code for the sake of dynamism, maintainability and ease of modification. WYSIWYG tools are great and powerful but they are to save the day not to endure. So IMHO in the end it will be always YES CODE.
I'm currently building a React Native app and I was wondering how much easier would it be to create a PWA that would live in a WebView inside a native app just so I could publish it in the App Store.
It’s very easy. Take your app, dump it into Capacitor. Done.
If you revisit your Capacitor-wrapper a few years later, you either take the update-dependencies-route or just start a fresh project and dump your PWA bundle in there.
Depends on how many native APIs you are using, such as in app purchases.
Most of the apps on my phone could've been a simple PWA. We need better design and UX for improving communication to the end users in order to make PWA's more discoverable.
Remembering good old times starting learn Meteor 8-9 years ago. I was looking for a silver bullet back then. My path was like Meteor->Angular->Ionic then I end up with React. I am not looking for a bullet anymore, I am happy with the light saber since then;)
Great component, thank you for sharing. I was working on a similar component called `react-monaco-tree`, which is waay immature right now. I took `https://github.com/BlueMagnificent/monaco-tree` as the base. Are there any list of all these 'file-tree' components for React?
Looks like the start of a great component! It's amazing to me how there is not a really good tree component that already exists, considering how ubiquitous the tree is in user interfaces.
Yes you are right. I wouldn't start that component if I had seen react-arborist. Since then I am looking for good file tree components. Thank you for the contribution, I will keep looking for the alternatives but in the mean time react-arborist seems like a great choice.
