Why single out the SASS version? If you compile LESS files you have the same option. I also think Bootstrap has a form on its website which compiles the CSS with the components you want, without having to install/run a preprocessor.
I've always used the Less version myself as a base for customization... lately, I'll npm it in as a requirement... copy out the bootstrap.less and variables.less into my project, update the references and work from there. It's relatively straight forward to do so... from there, I can comment out the parts I don't use. variables.less is mainly copied as a reference point... In my app.less, I include the bootstrap variables, then my own variables, then the rest of bootstrap, then my application less files.
At this point sass doesn't really offer much over less (other than a slightly stronger presence in the design community). I'm using node mostly, which fits in better for me, and makes less a better/tighter fit.
For better or worse, being able to bring in less, react and the like combined with SPDY/HTTP2 will bring some interesting development as things progress. Right now transpiling ES6/7 stuff to ES5 is probably the biggest bottleneck in terms of serving applications closer to as-is.
I've got no shame in having used Bootstrap on a number of client-facing projects (enterprise).
We've found it to be a great framework when used in the right way – Bootstrap SASS (personal preference) makes customising a doddle, and by making sure we only include components that actually get used, deployed code doesn't get too bloated. Supplementing with custom CSS can go a long way to getting rid of the "Bootstrap" look.
I was wondering about that as well - intrinsic vs extrinsic motivation - which would work better.
Did you do any research into it?
I'd also be curious if including the reward amount on the tag would increase or decrease the likelihood of an item being returned. Or does it decrease the likelihood if the reward is under a certain amount but increase it otherwise? And if that's the case, what's the amount, and is it a percentage of the item's value, or is it a constant?
Definitely - that's a great idea. We're currently looking in to a few strategies (aside from selling direct to the user):
- enterprise/businesses
- education (colleges & universities)
- manufacturers
- insurance providers
One angle that's certainly appealing is to reduce production costs even further (and therefore retail cost) to make a super low-cost way to protect items that have low value but high importance. Things like sketchbooks, coursework and so on.
I haven't heard of TrackItBack actually, but we know there are a few very similar products (TagBak, GadgetTrak, Tracer Tags). The problem is they're just so clunky - something we think we've solved pretty well.
