Development pace (roadmap for 2025?)

Thanks for the reply. Just so you know, “Does it mean that tabs would not come - absolutely not” is very different from “We don’t plan to add tabs” - nobody is going to link those two together, especially when you’re addressing implementing a feature that is akin to the tabs feature instead; and I would never have assumed tabs is still in the picture when you guys “don’t plan to add tabs”, hence the post asking why. Just like when you said there were no plans for Canvas above, nobody thought Canvas was still going to be a thing anymore until you acknowledge it’ll come someday. With this explanation, everything I said in the earlier post is 100% valid at that time. But good to know implementing tabs is still in the picture.

To address some of the other things you brought up individually:

Getting to it later is not the only reason for tabs, the example I gave was just what a lot of people do. Having the tab on the top bar also keeps it top of mind for the day without getting in the way of anything else and without getting more concentrated attention like a notification does. With that said, I’d like to see what your better solution for this is (perhaps your better solution can revolutionize how all browsers work yet none of the browser developers thought of implementing to browsers); adding something like a get-to-later list like YouTube’s Watch Later list is also not good - it works for keeping downtime videos, but not for something that actually needs to get to soon (otherwise people’s Pocket, Instapaper, Raindrop etc would not be filled with articles they hoard that they will never eventually read).

The very opposite of that is, some people open new tabs to get to it now (and has nothing to do with the current object), so that they don’t have to close the current tab and lose the current position in the middle of the object. This also means that the person wouldn’t forget getting back to the current object later because it’s not closed and it resides on the top bar, still top of mind.

All of these examples (and more) supports working with multiple objects at the same time without sacrificing screen space like how a split screen panel would, for those that do not have big screens. This point would also address your sentence "The ability to easily work with two objects at the same time is a different issue, and we’re solving it with the split-screen view. "

Of course, please do.
Just that nobody knew it was only “postponed” before your reply, as explained earlier it wasn’t implied that it was postponed. This would also address your sentence on “And why was this (split screen) prioritized over tabs”

I’m sure you knew this was not the point of my previous post… and this sentence you wrote seems like a strawman…

Oh please… me saying “facepalm” to express myself is not a jab; what is considered a jab is me saying: labeling me as criticizing the team just because I said “facepalm” is the lowest thing you can pick on <— this example would’ve been a jab if it wasn’t an example; or an actual jab on a different topic posted that you read directed at the Anyteam recently about hiring a specialist in dark patterns to come up with a massive downgrade and removed complete access to relations (not saying that that person can’t express themself that way); but me using “facepalm” gets me called out lol. Using facepalm is also a very accurate expression for my earlier post given what was written there and all the proof mentioned in the post to support my point (remember, this is before you reveal the idea of tabs is not dropped entirely in favor of split screen)

Regarding keeping it constructive, I’m not even sure how much more constructive I can be with my earlier post to show that tabs feature is more requested than split screen (again, this is before you reveal the idea of tabs is not dropped entirely in favor of split screen). What I wrote is certainly more constructive than the 2 YouTube video posts you got above after hearing you say there are no plans for Canvas feature… (nothing wrong with posting YouTube videos, I’m just using this example for you to juxtapose when you imply I’m not being constructive when I actually am).

And given the context, I feel like I need to say this: that this last section is not a jab as well, but me standing up for myself after being told incorrectly I’m taking jabs at you and for not being constructive when that isn’t even close to what happened.




Totally get you, I’m sure it’s the same for many people too (that’s why it’s the fourth most requested feature in Any Requests? out of the hundreds of requests that are there). But good to know it’s still going to get implemented, just that it was miscommunicated previously and sounded to everyone like it was dropped instead of postponed.

I apologize if my communication wasn’t clear—English isn’t my native language. When I said ‘don’t plan’ I meant that it’s simply not on the roadmap right now. But that doesn’t mean it won’t ever be. We’re aware of the need and do intend to find a solution.

Thanks for laying out your thoughts—it’s genuinely helpful. I agree that there’s a good chance tabs are the best solution. The Arc browser has tried to reinvent this, but they haven’t strayed far from the original tab concept.

Regarding the tone and the ‘facepalm’ comment: I understand that it’s your way of expressing yourself. I didn’t mean to come across as nitpicking or make you feel criticized for your frustration. I appreciate your passion for the project. Maybe it’s just me, but seeing ‘facepalm’ on something I felt was handled fairly was a bit much. But I see from where you are coming from.

While reply-ing to another post I came across this post of yours @anton. Reading it again it seems a lot whas on the roadmap in 2024 that as far as I know have not yet been added sadly. While I understand development is always rough and things (specially deadlines) change but I do wonder what the status is of the features from your post that where planned for 2024:

As far as I know adding templates to existing objects is not yet added. Only to new/empty objects?
Toggle and notifications are not yet added and I don’t know about inline latex additions.

What is the status for this split-screen feature? I have been using Logseq this year a bit and their split-screen was realy useful I found out (more useful than tabs even haha).

Judging this post I would assume the second half of 2025 is going to be insanely feature packed haha! :stuck_out_tongue:

But I do understand that development is very difficult and deadlines/roadmaps change all the time, so this is not my holding your words against you. :wink: Just me wondering if we could get an update for these features if possible but I totally understand if you can’t at this moment.

there was also “Tag as object” planned for 2024 :wink:

coding can be a lot of work. does AI help make it faster and easier for the Anytype team?

In general, AI aids development but does not enable the necessary code to be made directly (at least not with the tools I have been able to test at present).
As for Anytype, I imagine it’s the same. At least Razor has indicated that it uses it occasionally.