Hey hunters,
The whole team at Algolia is excited to announce InstantSearch iOS, making it easier than ever to build beautiful search UX in Swift & Objective-C.
This year we've been working a lot to bring the entire InstantSearch family together as one cohesive framework, so that product teams looking to bring their Algolia implementation from web to mobile would find the same rules, terminology & concepts across all platforms. Starting today, developers on iOS, Android, and the web can build the same great beautiful search experience for their users leveraging the same Algolia API & index.
We're excited to get feedback from the PH community - especially the iOS developers who have felt the pain before - and we look forward to improving InstantSearch iOS in the coming months.
Please tell us what you think, we love feedback!
-Nicolas
@vignesh_tronics Glad to hear you're hearing good things about us. Let us know who's saying such nice things and we'll be sure to send them a thank you note and a t-shirt!
Algolia's goal is to make great search possible for everyone. While worldwide lightning-fast search comes at a cost to us, we try to make Algolia as easy to use as possible and make the costs (which start at 'free') scalable in alignment with the success of a product.
Hey @dessaigne, we’re happy customers. What’s the difference between this and AlgoliaSearch-Client-Swift? Is InstantSearch-iOS mainly UI components/widgets? Or will this be its replacement?
Hey @timshim, I'm happy to answer that :)
That's a great question. InstantSearch-iOS is built on top of the AlgoliaSearch-Client-Swift and makes it easier for you to build UI search interfaces since it provides you ready-to-use configurable widgets. If you're only using AlgoliaSearch-Client-Swift, then you would have to write a lot more code and would have to deal with lower level search concepts (more details can be found in the blog post https://blog.algolia.com/instant...).
When writing UI, InstantSearch-iOS is the library to use, and you will still be able to have access to the properties at the AlgoliaSearch-Client-Swift level.
Now, AlgoliaSearch-Client-Swift can still be used in some cases. For example, it is UIKit-independent while InstantSearch iOS is UIKit-dependent. Also, AlgoliaSearch-Client-Swift could potentially be used on the server side for indexing.
Let me know if it makes sense and if you have more questions!
Hey there!
My name is Guy and I’ve been working on InstantSearch iOS for the past few months.
I’d be happy to hear your feedback and answer any question you have :)
Algolia