Have just this weekend started looking at the Playdate SDK proper (though while waiting for it to become public have been doing some prototyping of a 3D dungeon crawler in Lua using Love2D):
I eventually bogged down with Love2D, though, when implementing interactive menus... sure, I could cobble together something that worked, but it was a very low-level and tedious process, so I says to myself (I says) "Well, I'll hold off until the Playdate SDK becomes public, surely they'll have something much cleaner/easier!".
I try to first read (or at least, skim through) every developer doc / API / dev forum post I can when learning a new system, so I was a bit disappointed to see Designing For Playdate / UI:
Playdate doesn’t have a lot of system UI. There’s the Setup process, the Home screen, the Menu, and Settings. These are designed to be clear, readable, quick to use, and playful where appropriate. Beyond that, we’d like your games to be the star of the show.
We don’t provide many UI widgets for games to call through our APIs. Most developers like constructing their own buttons, menus, and sounds, to match their game. Some of the Playdate APIs will help with this, such as playdate.ui.gridview.
The game we're planning will wind up with all sorts of menus (both horizontal and vertical)... for interacting with shop owners, viewing/organizing inventory, etc. Some sort of menu scrolling will likely be necessary as well. Currently planning on using Lua as the implementation language.
It seems a shame to have everyone resort to rolling their own for this kind of thing. Has anyone out there come up with a generalized solution, or have advice/examples they can share, etc? I see the reference to playdate.ui.gridview as a hint, but just from looking at the API I have no clue as to how to actually use it. Not planning on using tile sets overall, we're hoping to maintain a 3D approach.
Any help/advice appreciated... thanks!