I posted a clip to bsky a few weeks back: https://bsky.app/profile/r.whal.ing/post/3lpyrm4vrqs2d
And Allieway Audio made some great Youtube videos about ORCA too if people would like to learn how it works in more of a tutorial format: https://www.youtube.com/watch?v=RaI_TuISSJE&t=446s
(I love the Dwarf Fortress background for this video, it absolutely nails the vibe)
Anyone from the area should check it out.
Something you'll find in both ableton and after effects are smart, adaptable panel abstractions/conventions. Both have fairly rigid application frames and large distinct sections where discrete types of work happen. But they also have panels where things can get nearly to a free for all. Think custom video effect controls, or individual midi instruments. There are norms (knobs look and work similarly), but things can get totally custom as well (custom graphs, etc). Lastly, at the very edge (~1% of use cases), there are ways to escape the constraints of UI entirely. AE has a code editor for things like custom wiggle animations. Ableton has M4L (which subsequently supports JS and possibly some C, IIRC). You can get yourself into trouble here in ways you normally couldn't: it's possible to straight up break things.
Greedy whitespace nonwithstanding, the most pernicious modern UI trend you'll need to buck is the idea that your UI should be simple because it is for simple people. Sometime UI is cluttered because of sloppy design or bad abstractions. Sometimes UI is cluttered because it's meant to empower people who think and care about multiple things simultaneously. Modern UI trends will tell you not to serve a man a steak because a baby can't chew it. Serve steak, babies be damned.
I guess that was mostly about functionality, and only adjacent to density. For actual density: vintage (2016ish?) 538 tables, vintage (pre 2010?) stockkeeping and cashier UI. These are basically TUIs with just a hair more polish. * Much less text heirarchy. This means even line heights, which means easy dense grid layouts. Achieve contrast with boldness rather than size, side borders, inverted backgrounds, etc. * The opposite extreme: very big items for very big tasks. Wide touch areas for each food item that a server can rapidfire tap through, everything else tucked to the side. * Thoughtful truncation: grid layouts often ask that things overflow. Do they elipsis at the end? Do they drop the middle? Do they condense 3 pieces of information into 3 smaller pieces of information? Etc. * Prefer text to icons for all buttons, menus, etc. A tab menu of just text is easy to parse. Icons add noise, and non-text buttons force users to speculate instead of read. * Intentionally non-responsive panels. Having fixed sizes for sidebars, panels, etc makes it easier to reason about how subcomponents snap to grid, and greatly shrinks the workload created by having to allow for fluid item reflow.
Various thoughts:
1. Consider defining best practices for solar and selling harder around that. I've got enough use for the board in hardwired environments, and can otherwise solve outdoor power issues, but having a recommended solution that I can trust to be solid would go a long way. "Using panel of X strength and battery of X capacity, get performance Y in Z conditions", etc.
2. I would probably preorder some of these, except the pricing is omitted. I have no idea how much these would cost. If they're 5 bucks, I buy a bucket. If they're 30, I buy a handful. If they're 100, I probably skip it. Etc. Withholding the price is a red flag, and I wouldn't share my email with an org that saw fit to withhold this info as the opening act. (edit: looks like the S1 is $55, so presumably this is more)
3. The LLM/agent aspect has no appeal. Assuming those costs are passed on to me / baked into every unit, the inclusion of AI is strictly downside.
4. It's not clear whether there are ongoing SaaS/storage/subscription costs associated with this, or what they would be. The FAQ suggests that forwarding data outside of the cloud will be restricted to enterprise-scale customers. This is also a red flag.
I think this can be successful in spite of all that. Particle definitely leaned away from hobbyists and into the larger ag-IOT market early on, presumably following money and stability. Totally understandable.
I guess my overall feedback is this: be upfront about the pricing and restrictions in a way that lets guys like me filter ourselves out upfront, instead of getting our hopes up. I've got a maker-tier budget, value data freedom, and am subscription-averse. It took me quite a bit of time and digging to uncover all the details in this comment, and I wish I hadn't spent the time. There are a ton of customers who are going to be totally cool with a $60+ board and a *0,000/mo contract for data forwarding. Court them directly.
Of course, I'd love to be wrong. If this is a $30 board with nearly-at-cost cloud storage and no REST data forwarding but yes bulk JSON download, then whoa, fuck yeah. Shout that from the rooftops too.
Either way, disambiguation would help.
He demo'd Captrice last week, to a bunch of friends here in Bangalore. And I knew he was going straight to the "infinite bikeshed", based on his tepid answers to questions like "Wow this is cool! So... Launch, when?".
Plus, you made m'dude earn his "First Internet Dollar". To whomever did the "buy me a coffee" thing... you're awesome! There is a stark psychological "before/after" of earning your F.I.D. Now he can't ever go back.
As someone stuck in his own Infinite Bikeshed, I take heart from this event, and hope to follow in his footsteps sooner than later :)
https://x.com/lindsaywise/status/1956170542601421040