Curious to hear about what external, customer-facing applications you have built with Palantir and any tips or learnings you would share.
1 Like
We just launched our first ever full-Foundry data app for our clients to do data exploration, export reports and get insights, and there are few things that come to mind out of the box:
- Keep your variable names verbose and unambiguous, preferably with directory like structure that mimic the pages of the app. We’re at 800 variables and I’m so glad we course corrected by variable #100
- Audit logs are miserable, if you need instrumentation plan it well ahead and consider creating actions / functions to record checkpoints / key actions
- In Workshop, Quiver embeds not good (super slow) if you’re doing anything more than super basic logic in the Quiver dashboard. Really recommend to sticking all logic in pipeline builder / code repo and charting in Workshop and Vega Widgets (the new AIP assist for Vega charts in Workshop is actually amazing, which I can’t say the same about most other piece of the AIP Assist experience)
- Even in Notepad, Quiver not good. If you want to give your users dynamic report building capabilities in Notepad, stick with Workshop + Objects inputs for most / all of the logic. Use Quiver just for charts and load them individually (vs full dashboard). Surprisingly hard to get a data report look good in Notepad, but we know the team is hard at work to improve it .
- Take advantage of the saved colours palette in the Workshop settings . Fairly recent feature but really great at keeping brand consistency across the board . If you’re working with designers, they’ll appreciate it
- We’re still discovering the sweet spot here, but treating Workshop apps as a software product with production-grade processes does improve stability.
We just onboarded in January so the entire team is super junior in Foundry, not sure this will resonate .