The 'consumerisation of the enterprise' is here to stay. Having a USP that is a negation of something beneficial and pleasant in UI pleasantness and that drives adoption is likely only to work against the success of this framework, let alone the narrower only 'internal' market reducing the role of the open source community in its continued development and their passion for it.
Show HN: Front-end framework optimized for internal apps
81–90 of 94 posts
Re: Show HN: Front-end framework optimized for internal apps
#82Just wanted to mention that I work on NimbusFoundry(nimbus foundry.com) which has similar ideas except we focus on auth, storage of data, and permissioning instead of front end. This is so that users can create apps within enterprise environments like Google apps for business easily.
Very cool - I like your idea to store all of the data using a Google Drive realtime document. But I'm not sure how you are able to handle authentication and permissions, e.g. limiting a field/model to only be visible to certain users. AFAIK read access to a document in Drive is all-or-nothing, and there doesn't seem to be a way to let a user only view a portion of the document. Are you only enforcing the access contr…
By permission, we mean that each team's data is hosted on a single document, and when you add a member, they can see both the data in the app and also binary files associated with that data. We don't try to do differing levels of permissions not supported by google
Re: Show HN: Front-end framework optimized for internal apps
#83Earlier quoted context omitted.
I don't like them at all. Yes, they look pretty, but it's an emulation of the worst aspects of paper forms. The grid-style form is my least-favourite paper form and I frequently find it confusing and difficult to fill out such forms correctly. Perhaps this is because the linear flow of the form is awkwardly two-dimensional, or perhaps because for anything beyond a trivial example, the layout becomes unnatural as the…
Be that as it may, this is exactly the type of form I routinely see people filling out on 80s-era WYSE terminals at airports, rental car agencies, the DMV, hardware stores, and so on. It seems like a lot non-tech people find them fairly easy to get the hang of.
Having worked in places where AS/400 terminals where the norm I'd argue that "non-tech people" don't so much as get the hang of it, as rote learn the system and then moment they step out what they have learnt fail miserably to recover. I've experienced push-back on updates to programs that take a five step process back to one or two simply because the person actually using the software didn't understand what typing the commands did and they weren't will to learn the new method.
Re: Show HN: Front-end framework optimized for internal apps
#84License? Scanned both the github and docs for any mention of it.
Added an MIT license to the Github repo.
Re: Show HN: Front-end framework optimized for internal apps
#85"It goes away with custom fonts" should be "It does away..." Other than that, pretty cool! There may be a space for this... Reminds me a bit of http://platform.qbix.com which we built to power social apps (on all devices). One tip: if you're going to make it for business, have the demo document the keyboard shortcuts to get around quickly, like in gmail. Ideally your "front end framework" could have a controller that…
Good catch, should be fixed now.
Re: Show HN: Front-end framework optimized for internal apps
#86I'd called that "lean and clean" instead of "boring". And I wish that more user facing apps would look like that, not just internal ones. Maybe it's just me, but all these flashy things, unnecessary effects, animations only clutters the screen and makes app harder and annoying to use. Functionality and ergonomics is all that usually matters. Well done, I'll give it a try.
Re: Show HN: Front-end framework optimized for internal apps
#87Looks very nice. I've been busy trying to make a dashboard for work with overview of various systems, I will definitely give this one a try.
Re: Show HN: Front-end framework optimized for internal apps
#88I really like gridforms for dense data-entry forms ( http://kumailht.com/gridforms/ ).
I tend to like typeform more, for anything form-like. (http://www.typeform.com/)
Re: Show HN: Front-end framework optimized for internal apps
#89I wish more things looked like this at work. There's apps that look like native apps, there's bootstrap apps, there's all the custom CSS floating around, there's whatever's new, there's the stock CSS sheet that comes with the plugins... Keeping to principles like this at work or for work environments would make it so much easier to have unity. I'm not saying everything should look like this, but that not everything n…
I work at a very large company and it's the same way. We have a team dedicated to keeping internal apps within certain stylistic and functional guidelines but the overall landscape is still an absolute clusterfuck. Some apps are built with bootstrap, some with pure, some with no styling whatsoever, different hexes for our company's primary color... you name it. Fragmented as all hell.
It's amazing in an "Agile" world, we still feel like we need to "configure" basic design concepts.
For internal apps: Structure could be one theme on one CSS framework. So much time is wasted on "design" (picking colors, lining things up) by people who don't know anything about design.
Re: Show HN: Front-end framework optimized for internal apps
#90Some feedback about the preview section:
/preview/typography: I was hoping to find out what font(s) I was looking at, but this page contains a history of typography. Looks like it's Helvetica? But I don't see the word Helvetica anywhere on the page. Maybe it's expected that the user will know why Helvetica is the right choice.
from /preview/grid : "A collection of classes to build grid based layouts with absolute ease. This is the simplest grid system you'll love to use." This feels weirdly sales-y for documentation.