I love Prismic, and I use the service everytime I can. Their team is impressive and very trustable in making the right technical choices.
The question I am asking myself since the availability of Slice-machine is : This is great but is it what I am looking for when using Prismic ?
For me, it is a content creation & management service, not a frontend library provider. It should provide the best when it comes to content creation, not content representation.
Of course, the two are linked, and maybe the difficulty in using Prismic API on the frontend has been a hurdle for newcomers, but IMHO Prismic should prioritize content creation features.
On that side, some features are lacking, with for example :
- Untranslatable property : a field that would stay the same thru languages version
- Searchable content : I think there are various external solutions we could use to make Prismic content searchable (inject in ElasticSearch or Algolia with webhook or homemade fetch), but it's not a trivial task.
- Auto content reindexation when the model is changing
- Improvement on the dashboard to search and organize when you have a lot of content (very difficult to browse our image library leading to a lot of duplicates)
The website is stating that funding will go in "content creation with slice." I hope there will be some money left to improve what I am really searching when using Prismic.