This might be something we’ll try in the beta editor, but no guarantees on when that will be.
One reason we haven’t implemented a collection type in Hopscotch is that for it to be useful, I think you’d need a lot of built-in functionality. This would clutter up the editor for more beginner users.
In the comments can you give specific examples of what you’d use collections for? That will help me think about what they would enable.
Also, feel free to shout out ideas about what to call them!
Again, this is not on the roadmap yet, it’s strictly exploratory
I don’t know what you’d call them or use them for, but I was thinking you would have an ‘Advanced Editor’ option, and if you turned that on, you would have a whole bunch of helpful, more advanced options.
Awesome idea! You guys are actually making premium worth buying now. In fact, if you end up getting that bug fixed that is making me unable to see shapes on my iPad, I think I could convince my parents to buy premium for the family using these new features as the benefits of upgrading. I’m composing an email to you now explaining the bug in detail, but it is the same bug @FearlessPhoenix is experiencing.
Woah! I’d use them for many things, most of which @Awesome_E already suggested. Depending on if you are planning to implement strings in lists or not, the use cases varies a bit.
I’d definitely love to see strings in lists as well in the future if that is possible!
And like the “Turn on the beta editor” toggle an “Advanced editor” toggle that would be a bit more easily accessible (perhaps you could put it in the editor itself) would be a super cool addition to the app!