5 ms·

You mean native mobile and desktop apps? That's definitely a much longer-term goal (and even more unclear :) but theoretically, given that Wasp is being designe

You mean native mobile and desktop apps? That's definitely a much longer-term goal (and even more unclear :) but theoretically, given that Wasp is being designed as stack-agnostic framework, it's possible which makes it really exciting. We thought about it a bit already and definitely not 100% of concepts from the domain of web apps would apply (e.g. routes maybe don't make sense in mobile apps), but there is still a lot that could be share. Maybe Wasp could also generate some SDK you could use from your native mobile code. That's all long-term stuff so really hard to know, but we imagined we'd first focus on getting to 1.0 with React & Node, then add support for more client/server stacks (e.g. Vue and Python), and then go towards mobile and desktop.

jstummbillig 4y ago
Mobile, yeah. The only thing I feel is super important there is getting push notifications going and both iOS and Android are sadly sabotaging the Notification Web API. Other than that a PWA would be totally sufficient for all my use cases and that seems to align really well with what you are building with Wasp. Certainly keeping an eye on this one.
- matijash 4y ago
  That's a good point, I'm not so much in mobile these days so weren't aware of push notifications issue. Also great to hear PWA can cover a lot of cases, that would definitely be a natural first step towards mobile.