TLDR:
The premise isn't ambitious enough, the use cases seem thin, and the lack of marketing pop reflects a lack of distinct USP. But, I'm encouraged to see someone trying technically ambitious work like this because its barking up the right tree.
Long version:
It seems like your value prop is possibly about how various workflows are organized vis-a-vis each other, but that really doesn't come through in your marketing. Rethinking the info architecture and organization of information in support of more efficient and focused workflows is a promising place to go but everything in the screenshots shows me things I've already seen. Each of the items in your marketing had me going 'I already have something for that, and this is probably way worse'.
I'm not seeing ideas in here yet that are sufficient to consider worthy of the technical challenge you've undertaken - that is, an environment where you have complete control over apps.
For instance, app grids are terrible, even the notion of apps is terrible because apps have their own distractions and workflows span apps. I'd expect something that sits at a layer below (web)apps to be able to do something about that, like extract useful things from apps without showing me the whole app. You need to flex your unique position with product approaches like this.
The main idea I'm seeing besides organizing is the time/task system. This looks a bit like single player Clockwise [1] and raises more questions than it answers. The main concern I have with this is that any auto-schedule is going to be rather rigid and force me to babysit it to meet my expectations. The real test of systems managing our time is how adaptable they are to the uncertainties life throws at us, not the creation of rigid work plans. In this case it would be good to shift your marketing (& product) to how your product adapts to various scenarios and use cases in the user's life, rather than presenting an idealized way of working that users have to adapt to.
For whatever it's worth I've done some thinking around organizing OSes differently in my Spaces concept [2] and I'd guess you're probably aware of MercuryOS [3] ideas. Both of those start from premises far different than our current paradigm and show the implications of how organizing information differently creates unexpected new ways to use our devices. I would encourage a similar level of ambitious premise to justify this level of technical undertaking. Glad you're in the arena doing this work though, as the technical undertaking creates the opportunity for more ambitious ideas to be possible.
[1]: https://www.getclockwise.com
[2]: https://nickpunt.com/blog/spaces
[3]: https://www.mercuryos.com
The premise isn't ambitious enough, the use cases seem thin, and the lack of marketing pop reflects a lack of distinct USP. But, I'm encouraged to see someone trying technically ambitious work like this because its barking up the right tree.
Long version:
It seems like your value prop is possibly about how various workflows are organized vis-a-vis each other, but that really doesn't come through in your marketing. Rethinking the info architecture and organization of information in support of more efficient and focused workflows is a promising place to go but everything in the screenshots shows me things I've already seen. Each of the items in your marketing had me going 'I already have something for that, and this is probably way worse'.
I'm not seeing ideas in here yet that are sufficient to consider worthy of the technical challenge you've undertaken - that is, an environment where you have complete control over apps.
For instance, app grids are terrible, even the notion of apps is terrible because apps have their own distractions and workflows span apps. I'd expect something that sits at a layer below (web)apps to be able to do something about that, like extract useful things from apps without showing me the whole app. You need to flex your unique position with product approaches like this.
The main idea I'm seeing besides organizing is the time/task system. This looks a bit like single player Clockwise [1] and raises more questions than it answers. The main concern I have with this is that any auto-schedule is going to be rather rigid and force me to babysit it to meet my expectations. The real test of systems managing our time is how adaptable they are to the uncertainties life throws at us, not the creation of rigid work plans. In this case it would be good to shift your marketing (& product) to how your product adapts to various scenarios and use cases in the user's life, rather than presenting an idealized way of working that users have to adapt to.
For whatever it's worth I've done some thinking around organizing OSes differently in my Spaces concept [2] and I'd guess you're probably aware of MercuryOS [3] ideas. Both of those start from premises far different than our current paradigm and show the implications of how organizing information differently creates unexpected new ways to use our devices. I would encourage a similar level of ambitious premise to justify this level of technical undertaking. Glad you're in the arena doing this work though, as the technical undertaking creates the opportunity for more ambitious ideas to be possible.
[1]: https://www.getclockwise.com
[2]: https://nickpunt.com/blog/spaces
[3]: https://www.mercuryos.com