1
tl;dr – it's a way to build simple-but-slick web apps that are powered by API automation behind the scenes, without writing code.
No code? It's because our traditional users are technical-but-not-engineer types like Security Analysts and IT Managers. So this new way of building front-end experiences follows that lead. But as a more technical maker myself, I've been really surprised at how well this works and scales, and we’re seeing teams like Engineering and DevOps increasingly adopt also. I think maybe it's because us software people most intimately understand the long-term/hidden costs of code… maintaining, bug-fixing, deployment, etc.
Anyway, If you’d like to check it out…
1. there's a usable version of a demo app mid-way down the page above, and then clicking the "How was this built?" button shows you the equivalent of source-code, i.e. the visual automation underpinning everything.
2. we have a forever-free tier, which you can sign up for here and play around for real: https://www.tines.com/sign-up
I’d love to hear any and all feedback! We love a good dose of HN-style tough love, which we certainly received our fair share of last time we surfaced here :-) [2]
- Stephen
---
[1]: Tines – no code automation [2]: https://news.ycombinator.com/item?id=30249518
My weekend project was this edit-in-place style invoice maker, with one button PDF generation and localStorage for everything. Aside from the PDF generator step, everything is jQuery powered and there is effectively no backend. This is (I suppose) an Alpha version, only really tested on webkit (iPad, Safari, & Chrome).
Feedback would be great: it's my first foray into web app development and I'm finding it hard to look at the page with fresh eyes—although I have my doubts about its usability in certain areas! All comments are welcome.
Part of me is tempted to attempt a platform for edit-in-place documents of this nature, I'd be interested to know if there is a similar approach taken elsewhere.
Many thanks, Stephen
(Note that this is a sort of follow up to my Ask HN http://news.ycombinator.com/item?id=2394319. I've taken on board the excellent advice there and have been doing lots of reading and experimenting. Want to get into the habit of shipping things ASAP though, so this is a small first step in that direction; it's also a tool that's handy for me.)
Of late I've come to realize that I should have done computer science. I didn't, and studied engineering instead: now I find myself in a (good & hard to get) post-university industrial career, but ultimately uninspired and dissatisfied. I by no means hate what I'm doing, but I can feel my inner hacker bursting to get out frequently (e.g. today as I tinkered around with some VBA at work i enjoyed—pathetically—the most satisfying part of the week so far!)
I have a semi-relevant background, in that alongside engineering in university I did a lot of freelance (frontend) web design, and developed a real passion for UX, design, typography, etc. I am also very numerate and have a basic grounding in programming (C, Matlab, Basic). My dream would be to be involved with a web app startup.
The long awaited question is: how best to proceed? Should I learn Python or Ruby and brush up on my front end design again, and attempt a few small projects in my non-work time? Should I quit my job tomorrow and go back to university for computer science? Can the hacker ethic find a home outside computers? Are faraway hills always greener?