Deep Q & A for friends, family, and strangers. My goal is to create a space where people can get to know each other a bit more deeply and spark conversations. Would love some feedback!
Ideally you'd use Tandem along-side your text editor. It's not meant to replace writing code - I think in most cases it's easier to write code by hand than use a visual tools. Though, I think there are cases where it's easier to use visual tools against a live application preview for making small adjustments - that's where Tandem fits in.
Here's a better video demo to help demonstrate this:
Thanks for the feedback! I figured that short videos throughout the website would be enough to describe visually what Tandem is, but a short video at the top would probably be better.
And yeah, there are a ton of UI design tools out there on the web, it's been my #1 concern when building this thing out because they all promise similar tooling. Though, I'm trying to position this app as more of an Atom, or VSCode-like since it's geared to be another kind of extensible development environment. I figured that open sourcing it would be a first good step for that since developers would probably need to understand the internals before writing plugins for new UI tools, code writers, etc.
I went ahead and added a "Fork me on GitHub" badge to make it more clear that this is open source.
Sorry for the confusion there, I went ahead and clarified the descriptions.
Tandem runs any application, but needs the appropriate extensions in order to write code. It has the capabilities of writing PHP, but that isn't implemented yet.
The code writing aspect of Tandem is really just a small feature of the whole application - The focus of Tandem is really to provide a preview (or many previews) of your application with tooling that makes it easier to fix visual bugs.
It is a bit like WebFlow, but focused more-so on the coding aspect. Tandem integrates with your text editor, encourages you to write code instead of using the design tools to all of your UI work -- they're mostly there for UI adjustments, and to create features that are hard to code by hand.
Thanks for the heads up - the todos example should be fixed. Right now the todos example is pretty simple - it just hooks up with a socket.io (master) server which re-broadcasts all operations to each connected client.
I'm a front-end developer, and there's lots of service features to think about when building a single page app:
Should app data be generated from the server initially?
Should the app support offline read-only mode?
Should the app support realtime data?
Should operations be batched and sent to a data source?
Should the app be isomorphic?
And others. I built crudlet to help encapsulate services so that these sorta features can be added anytime without
affecting the rest of the application.
That, and also to help decouple applications from a particular service. For instance, it'd be pretty easy to
swap firebase with parse, or socket.io for pubnub if you want.
They definitely solve similar problems. Bigger difference is that crudlet acts more like a utility belt library for interacting with service adapters that
support the same operations. You can really do just about anything you want. For example, here's crudlet used as an event bus system:
App: https://hey.shaya.so/ Website: https://www.shaya.so/
reply