gr2m
commented
7 years ago Hey @alterx, welcome to Hoodie :)
I'm currently developing an application that will allow the visually impaired to get a notification when they arrive to their bus stop and I'd love to use Hoodie since mobile internet connections are flaky and we don't want to loose the ability to provide a good user experience to people that will rely on this app.
This sounds like a great project!
I’ve one technical question about "the visually impaired get a notification when they arrive to their bus stop": I assume you want to app to be able to run in the background than? You might need a native app for this. Maybe Service Worker can do that already, but that would limit you to Android devices at this point. Hoodie can be used for native apps as long as you use web technologies, we don’t have native Java/Swift clients yet.
Global, publicly available routes
Defining public routes that expose read-only data from a database is possible with Hoodie today.
What we don’t yet have (but could work on right away) is a client API that would provide the same API as hoodie.store, but for custom databases. Our plan is something like this
const routesStore = hoodie.store.open('public-routes', {onlineOnly: true})
routesStore.findAll().then(renderPublicRoutes)These routes can only be modified by administrative users via a CRUD UI.
The UI part would require some work. Ideally this would be possible directly trough the Hoodie admin dashboard but we are currently not working on it, we want to finish the plugin architecture first, then build the admin dashboard as a plugin.
For the time being, you could build a custom plugin for it with custom routes etc, but I’d need to have a look into it, I expect some bugs here and a few things that would still need to be implemented, but I’d be happy to provide guidance as needed.
Public user accounts in which people can store their favorite routes, we want these to be available offline for sure.
What do you mean with "public" user accounts? What is possible today is that every user has their own private store and they can store any data in it that will also work offline.
We don't expect a lot of users initially so we can afford some experimentation with the technologies
Great :)
I'd rather use Hoodie and fix some hiccups than build my own sync engine.
Good choice! I’ve been there, don’t.
In case Hoodie becomes to much of a barrier, you can still use PouchDB directly and build out your own backend. You can still use parts of Hoodie like only the account module for example, Hoodie’s architecture is very modular.
Do you think this is feasible with Hoodie in its current state?
I think it’s feasible. It’s definitely an app within the scope of Hoodie and the parts that are missing have already been thought about and can be worked on right away as far as I can tell right now.
Do you think there will be any issues scaling up? Also, what are the hardware requirements to run a Hoodie app + CouchDB reliably? I've seen a couple of related questions but I can't seem to find any numbers.
I don’t see scaling issues right now. What would be problematic is when you would need lots of data sharing, but it doesn’t look like it at this point. Also CouchDB 3, which is in the works, will resolve these problems, too.
In terms of Hardware requirements, that is a very good question and we should come up with a good answer and add it to our documentation :) The Hoodie app itself is basically just a hapi application, it runs everywhere, including read-only deployment targets like Heroku and now.
For CouchDB, let me ping @janl.
One thing you could check out is , does that help already?
I've seen that there's a plugin system in the making (there's even an open PR) Is there any ETA on that?
The plugin system itself is working, ETA could be as early as Monday. I need to clean up the pull request and add documentation, other than that it’s all done!
I know that you can extend the functionality by adding a module constructed as a hapi plugin to the path
hoodie/serverbut what if I want to add multiple "plugins"?
A hapi plugin can load more hapi plugins, there is no limit in terms of how many routes you can add etc, the logic can be spread across multiple files, too.
Do you have any idea of what's the max amount of users we can support per couchDB instance? (I know this is a tricky question to answer, but I'd thought you guys would have an idea from your experience with minutes.io)
minutes.io runs smoothly with thousands of active users using one CouchDB instance.
Let us know if you have any further questions!
alterx
I'm currently developing an application that will allow the visually impaired to get a notification when they arrive to their bus stop and I'd love to use Hoodie since mobile internet connections are flaky and we don't want to loose the ability to provide a good user experience to people that will rely on this app.
In order to achieve this we need to create:
We don't expect a lot of users initially so we can afford some experimentation with the technologies and, to be honest, I'd rather use Hoodie and fix some hiccups than build my own sync engine.
So,
hoodie/serverbut what if I want to add multiple "plugins"?Thanks in advance (and sorry if this is not the right place to ask these kind of questions)