31–40 of 42 posts
DabbleDB again. Don't break my heart.
Earlier quoted context omitted.
OK, let's try this for a title. "Build your database with online spreadsheet" I've already updated this to the website.
That doesn't quite read correctly. "Build your database with an online spreadsheet" or "Create your database as easily as a spreadsheet" or "Build with the power of a database and the ease of a spreadsheet" Ps. Love the idea for the project, I have been looking out for something like this for a while.
We try to make the sentences as short as possible.
you should hire a native english speaker to write your marketing copy
you should hire a native english speaker to write your marketing copy
We hired a native English speaker to edit most of our copies.
There are some grammar mistakes and you can hear mouse clicking when he switches slides.
The information is there, but I think it needs a bit more polish in terms of phrasing ("Special need is nothing special.") and a proper speaker.
Earlier quoted context omitted.
I love the idea. the interactive guide is horrible. far from simple. Sorry for being blunt.
Hi, did you run into some problems in the tutorial? Or because the steps of the tutorial is too complex?
A few more things:
- It was hard for me to get into design mode again after having tried the form view. I'd make that more prominent. Right now I think it's only in the context menu for the entities, not for the whole db however.
- I see forms, but do you have (dynamic) list views as well? How do I format / generate them?
- Try to get rid of all the "leave this page" browser warnings.
- paragraph text fields behave very odd in Chrome (graphical issues after resizing, I think it also cut some pasted text). I also think rich text capability might be critical there, but I can understand that you wanted to avoid that beast at first.
In general I like the approach - I think it's a very valid business idea to try to give benefits to all those businesses with Excel 'workflow applications'. The ability to do multiuser editing might be a big enough benefit alone to get some customers - maybe you could accentuate more on that. IMO however the UX from the developer end needs a lot of streamlining.
Earlier quoted context omitted.
Hi, did you run into some problems in the tutorial? Or because the steps of the tutorial is too complex?
Trying to answer here for him: I ran into troubles with the third field added - the demo didn't react anymore, I couldn't type in the field name. Also I agree that it should be a bit less restrictive. For example it only accepts the step when I actually type in "Customer". I'd prefer arrows and a fixed help box instead of the overlays - as it is at one time had to look around where it wants me to go next. A few more…
1. What browser/OS version are you using? I would like to reproduce this issue.
2. It's in the context menu you mentioned, and in the upper right corner of the form. We should find some way to make it more prominent.
3. The dynamic list views are generated automatically. When you finish designing a form, just click "4. We added the "leave this page" warning because a lot of users have mentioned that they accidentally click on the exit button.
5. There's some special feature that we added to the copy and paste function that might confuse new users. I think we need to disable it by default. The feature is mean to match the field names from the source with the field names in the Ragic form, and put values from the source to their corresponding fields.
Really appreciate the feedback, please let me know if there's any other advices. I can be contacted at jeff at ragic dot com
I strongly recommend you offer a demo without needing to sign up. I was intrigued enough to take a look, but not enough to go through a sign up process.
We had a sandbox account log in at the registration page, but after some testing we found that it made a lot of people who would have signed up just go to the sandbox instead. The original page is here: http://www.ragic.com/intl/en/registerSandbox For people who would like to use the sandbox instead.
See how they have done it on https://hollyapp.com/
It took me a while to find that link again, but I thought it was worth it as an example.
Good luck.
Earlier quoted context omitted.
Trying to answer here for him: I ran into troubles with the third field added - the demo didn't react anymore, I couldn't type in the field name. Also I agree that it should be a bit less restrictive. For example it only accepts the step when I actually type in "Customer". I'd prefer arrows and a fixed help box instead of the overlays - as it is at one time had to look around where it wants me to go next. A few more…
Hi, 1. What browser/OS version are you using? I would like to reproduce this issue. 2. It's in the context menu you mentioned, and in the upper right corner of the form. We should find some way to make it more prominent. 3. The dynamic list views are generated automatically. When you finish designing a form, just click " 4. We added the "leave this page" warning because a lot of users have mentioned that they acciden…
4) How about a save-by-default stance? is versioning and rollback hard to implement on your stack? (those two characteristics should be used together IMO) Alternatively I'd just implement a message that asks whether to save, forget changes or cancel.
seems like you will swim in money in a few months if you reach the right target market...