Kexi Project – an open-source visual database applications creator
kexi-project.org
kexi-project.org
* roadmap : planned features with rough timeline, and an option for the public to be able to request/prioritize/vote.
* comparison : a list of features of MS Access that Kexi can do, and more importantly, what Kexi can't do yet. Its completely ok to state that something is in the roadmap, or even that it currently is not in the works.
This is very important to potential MS Access users or those who understand that world, who might consider migrating.
For the other thing, I don't know if it's up to date but there's this page: http://www.kexi-project.org/wiki/wikiview/index.php@KexiComp...
https://bugs.kde.org/buglist.cgi?quicksearch=kexi%20severity...
Coincidentally, yeah, comparison and feature sheet is what we want to have soon, probably near the come back of the Windows version.
And we're looking for talented volunteers to prepare a new more modern web page. Something like https://marble.kde.org and mobile-friendly.
last couple projects of mine have been rebuilding access and filemaker stuff for the web. filemaker, as nice as it is in some respects, introduces relatively high licensing costs (at least relative to my client's test pricing). i guess had he used kexi it wouldn't have been a problem... :)
I'll try to answer some questions.
PS: came here alerted by this post :) https://www.reddit.com/r/hackernews/comments/3p8e9z
My gut feeling says the Access world is dying rapidly, and if that is true, a * nix version playing catch-up does not have a bright future.
I've developped a few web applications and forms along the years, but never could I get something together as quick as I did when I decided to try MS Access, for a prototype app. E.g. I've used Django, yes I can create forms pretty quick, but with Access with _no programming_ and 2-3 hours of familiarization I could put up forms with create/edit/delete functionality in something like 30 minutes, along with the underlying schema.
I haven't touched it since I created that prototype, but I was left wondering what's the equivalent in the webapp world, for the basic CRUD use-case.
100% point-and-click creation of new objects, relationships, forms, etc... Easy baked in reporting, import, and export. Workflow automation totally configurable without code. Thousands of apps on the AppExchange to add interesting features. And of course, when you need to add code, it's very easy to get started if you know OOP.
If you frequently have to create quick web-based systems that would have been MS Access, go check out https://developer.salesforce.com/trailhead, grab a free SFDC org, and build something cool.
It is proprietary and mostly focused on large companies.
Full disclosure: I work for Mendix
Still if I look at your site (Mendix) and my mindset is "I just want a few tables and a few simple forms", my guess is that if I were a non-developer I could be a bit overwhelmed. But as you say Mendix targets large companies.
FileMaker has its strengths, but the web isn't one of them. The results are subpar in my opinion and will always feel like a rapidly converted and FileMaker-branded, bloated and slow webapp. Just look at the generated HTML - it's an endless tree of nested divs.
On an awfulness scale from one to ten, it ranks as cthulu.
But Alpha Anywhere seems to have a long history and some traction, that's good to know.
Ruled by what now? Sounds like a HN pipe dream.
It's a bit clunky but you can run Access applications in a browser [1]. So Access is no longer synonymous with "shitty little data entry desktop application".
[1] http://www.brighthub.com/computing/windows-platform/articles...
It's not complaining but: if the percentage of people using such apps isn't increasing this is maybe also because of average level of technical education among computer users decreasing. Average user wouldn't operate at this level of specialization. Even scientists... those I know don't reject using simple spreadsheets risking numeric inaccuracies. Weak and prototype tools become the standard for them.
So simple spreadsheet apps (excel-like) that got very feature-laden over the years (statistical stuff, etc.) that clearly introduce on a concept of a strict matrix structure are very popular and they don't get replaced by web interfaces. Conversely, the web interfaces try to emulate the original UX with more or less success (Google Sheets, MS Office online).
Simplistic explanation of Access type of apps could be that they introduce data types and more on top of what's know in spreadsheets. There's always market for that but the demand needs to be realized (created?).
Ideally the database type of apps could learn some agility from the spreadsheets world. Newer MS Accesses offer implicit adding of fields in a 'spreadsheet' way in the data view and altering form/report design in the data view as well. I'd like to have that in Kexi too. Maybe even the app should welcome the user with an empty sheet of cells by default?
We have a place for discussions on the forums https://forum.kde.org/kexi and also mailing lists if someone is interested.
If it requires switching to other platform then it requires effort (1)to find new platform (2)migration to new platform and results in dying slowly.
Doesn't support database creation, just Form building.
Filemaker has this for iOS, but not android.
It may exist, but I haven't see it.
In some way it's even better the 2006's solution isn't in use, we can start fresh. For this volunteers are needed: web developers/users/designer, not necessarily C++ hackers.
Some jquery/bootstrap components can make the data grids and forms work well.
Kexi picked SQLite as the default backend in 2004, and it was a good bet. For native mobile there's Qt Quick for the GUI with which large part of Kexi is compatible. A database creation/handling layer has been extracted years ago and now it matures under name KDb: https://community.kde.org/KDb