I’m evaluating Baserow as a means of sharing databases between members of my family. One of the most important use cases is as a shopping list application. We’d want to create a shopping list on one device and be able to read and update it on our mobile device(s)
However, when we bring up the database on our phones, we are unable to edit any of the cells. Nothing happens when we (double?)click on the cell. I would expect to have a keyboard pop-up.
I’ve tried with both the Brave and Firefox browses.
We do not offer mobile support for Baserow itself at this point in time.
You are correct, it seems like you can’t edit fields just by clicking on them, or at least it doesn’t open your keyboard.
One thing that does happen to work is holding your click to open the context menu of a cell and then clicking on “enlarge row”, which opens an edit modal in which you can in fact edit the cell.
I know this is quite cumbersome but maybe this helps a little as a workaround for now?
Another thing that might improve your mobile experience is to view the page in desktop mode. I know my chrome browser supports that by just clicking on the top right option button and selecting “Desktop Site”.
Again, not ideal but it might give you a slightly better experience.
That’s correct @Alex. We don’t have any concrete short term plans on improving the mobile experience for Baserow. This is definitely something that we want to do in the future though because we want Baserow to work on smoothly on mobile/touch devices as well.
I’m using baserow to run a small business, and sometimes I need to pull the information up on my phone to try to make a sale. Would love to have it optimized for mobile in the not too distant future.
One of the things I have been looking at is Lowdefy it can take a bit of work to understand but it would allow you to quickly make a mobile friendly interface to your database.
Am I correct in assuming that there is no mobile version yet for Baserow? This is serious limitation. Need to be able to access data on our phones. Is this planned?
Thanks. I noticed in that issue that they mentioned the, “With the row “expanded” view”. How do we get the row expanded view? That would help alot.
EDIT: I did notice a way to see the entire row on desktop with an icon in the ID field. I guess that’s the expanded view. Unfortunately, it looks terrible in mobile. Can’t even see the row data. Really, Baserow is completely unusable on mobile. You’d get alot more customers, if you had a decent mobile experience. Most people need access data from their phones nowadays. The only way I can see doing this with Baserow is to sign up with Retool and create a mobile app using the API from Baserow. But this is a big pain.
Thanks. Yep, I saw that. See my edit above. Works great on desktop. Unusable on mobile. You can’t even see the data. But, you can probably fix this, so mobile would work. The problem is that you fill up the screen with comments/history information and block the actual data (the data is hidden beneath the comments/history - so it’s basically invisible). Howeve, with some slight modifications the expanded row view, would solve the mobile problem, per the issue linked to above. Not sure why this is not fixed. Fix seems easy. On mobile show the expanded view only with the data (hide the comments etc.)
yeah, I’ll try again. As you can see from the screen shot, though, it’s a really bad UI. That arrow to view the entire data is tiny and hidden basically. On mobile, they should just hide the comments/history. This is secondary to the data. So the UI should be the opposite. Show the data on top (primary view) and then a button to show comments/history, or just hide these on mobile.
So I played around with the expanded row a bit more on mobile, and for sure, just fixing up this UI a bit would give a decent mobile experience. Not great, but at least totally usuable. Still there are issues with navigation and how it should be done on mobile. But the expanded view certainly has the germs of a decent mobile solution. Wondering why nobody bothered to follow up on the issue you linked to above? Seems abandonded.
