News for hackers. Stuff that matters.

jayjohnson

Know any tips for my new product's rollout?

I am looking to launch a new product website, but I do not have extensive experience with how to grow a customer base from scratch.Phase 1 - Rollout and Launch: During this initial growth phase, I know I need to continually improve how each customer type finds my product, and I need to make sure that my product is tracking "enough data" for generating some reports that I can...

( Read More... | no comments | on HN )
Re:Our Startup can help other Startups build an MVP on Monday April 21, 2014 @03:18PM (#7623061)
We are interested in figuring what to build/how to market this and both of you have had great feedback for us.

I was reading your post on https://news.ycombinator.com/item?id=7321013 and that sounds like it's spot on what we are looking to do right now.

Are you looking to build something still? If so here's my email: [email protected] let's get started!

Re:Our Startup can help other Startups build an MVP on Sunday April 20, 2014 @10:29PM (#7619446)
This is good feedback with great solutions. We are novice on all things marketing and advertising. Would you be interested in jumping on a hangout/skype to discuss more with us?

Jay

Re:Ask HN: Idea Sunday on Sunday April 20, 2014 @10:19PM (#7619406)
How intrusive would the developer environment have to be? We're a "host your own REST service" development shop so deploying and testing your own GitHub repo is done with a dashboard from a web page. In our eyes, everything outside of code development and code hosting should take place in a web page complemented with command line tools for advanced control.

The feedback we have heard is the editor of choice is near-and-dear to a developer and would be difficult to force a new tool on anyone to edit code. Code hosting has a good solution with GitHub too. Which leaves testing and deployment up to the platform. Since we focus on giving two free REST services for publishing your own Jobs we put the deployment and testing into our web dashboard (and cli tool). Testing a REST API is easy and already integrated into our dashboard similar to Postman. The only code a developer has to write is a Job which is just 3 simple parts (inputs, outputs, and tasks). For us we wanted the .Net debugging power for every developer from our dashboard so we built it to identify tests that fail validation based off your test inputs and outputs versus your test's expected outputs.

Let me know what you think here's our beta vision based off our feedback for quickly developing and deploying REST API services for your own Jobs: https://flowstacks.com/developer/

Cheers

Re:Ask HN: Idea Sunday on Sunday April 20, 2014 @06:13AM (#7616393)
Interesting idea. So we're in Beta and looking for good ideas like this to build showing our technology. For background, we take a user's GitHub repo and deploy them into REST API endpoints hosted on EC2. Each REST API is already paired with a database with SQLAlchemy. Clients invoke their REST API to publish their code as a "Job" requiring 3 parts: inputs, outputs, and tasks to perform (states). Those tasks can be whatever is necessary for your tdd and we test Jobs directly from our Web Developer Dashboard or with our cli.

I could see something like a Final Exam repo setup where your students fork it for development and then testing based off the same code and tests are shared already in the repo and can be invoked for grading from our cli or the Web Developer Dashboard.

Some More Information on FlowStacks (https://flowstacks.com/)

FlowStacks Hello World Example https://github.com/FlowStacks/hello-world

FlowStacks Tests https://github.com/FlowStacks/hello-world/tree/master/tests

Endpoint-specific Database Schema https://github.com/FlowStacks/hello-world/blob/master/schema...

Example Job Inputs https://github.com/FlowStacks/hello-world/blob/master/src/ra...

Outputs: https://github.com/FlowStacks/hello-world/blob/master/src/ra...

Example Job Tasks to Perform (States) https://github.com/FlowStacks/hello-world/blob/master/src/ra...

We also support Jobs integration with Redis https://github.com/FlowStacks/hello-world/blob/master/src/ra...

Contact me if you have more questions.

Cheers,

Jay

Re:Our Startup can help other Startups build an MVP on Sunday April 20, 2014 @05:13AM (#7616314)
All great points, and just goes to show we need to be updating the website and docs more actively. So for starters here’s where we are: we're in week 7 of beta where the core focus is giving developers a free public sandbox for two hosted Endpoints + a single database per deployment all for free. We have two tools for using FlowStacks:

1) The Developer Dashboard (https://flowstacks.com/developer/) is for testing new code, managing all endpoints, deployments, database schema (coming this week), and account details from a browser.

2) The command line interface (https://github.com/FlowStacks/cli/blob/master/fs.py) for full API capabilities, scripting, and the latest error handling. We are a command line shop, so we use this to find bugs, and it already reports things like bad JSON syntax, API Validation, Python syntax, Exceptions, and as many other silly errors that really annoyed us.

We’re still building the advanced deployment and database management into the website, but all of the tools are already working from the command line. We are also close to releasing a working Django webserver that uses any Endpoint-level API file (https://github.com/FlowStacks/hello-world/blob/master/api/wo...) for quickly mapping Javascript strings through Django into a working Job[1] hosted on any FlowStacks REST API. This factory style approach to building Jobs extends beyond Django, but since we’re a Python shop we went with it first. We planned on knocking out Rails next, but we are flexible.

Why FlowStacks? As developers, we wanted to have a Job hosted on a REST API where the API Inputs/Outputs can be Job-specific, and we did not care where the Job executed. For us, this API standardization has made us able to quickly build our own dashboard using and testing FlowStacks Jobs like any developer. We want the Dashboard arming developers just like .Net for debugging where streamlined testing drives features out faster, and it has to be simple to use (no Jenkins/Travis it’s all JSON black box testing similar to Postman). We built the command line interface for handling build regressions and showing how to use the FlowStacks User API and REST APIs from the command line. We also built the cli and dashboard for deploying your own GitHub repository into a REST API where your Job code defines the hosted API(dashboard build is coming this week). Jobs are easy to write. There’s only three parts to a Job: inputs[2], outputs[3], and tasks to perform (states)[4]. This allowed us to build some of the first Jobs like our Twitter Poster Job[5] because we did not want to login to Twitter. We also include Redis integration for any Jobs[6] out of the box already, and we use redis extensively for caching and publisher/subscribe patterns.

Our data policy is very open based off feedback we hear. Right now, we use Python’s ORM SQLAlchemy for any schema integration into your REST API’s database instance (https://github.com/FlowStacks/hello-world/blob/master/schema...) and Jobs can also use your new/legacy database(s) outside of FlowStacks. We just need a network connection. Here’s our example included in the Hello World for setting up a REST API Job to establish a connection to any database outside of FlowStacks: https://github.com/FlowStacks/hello-world/blob/master/src/ra...

Post Beta we plan on launching the on premise offering for Enterprise solution development and deployments on site. We can support these if needed, but for now we have it as a lower priority for us just trying to build a larger developer audience. Lastly, we are looking to build something with this, and we always want to hear some more great feedback like above.

Email me and let’s set a time to discuss this.

Cheers, Jay

More References:

1 – API Job fields: https://github.com/FlowStacks/hello-world/blob/master/api/wo...

https://github.com/FlowStacks/hello-world/blob/master/api/wo...

2 – Example Job Inputs: https://github.com/FlowStacks/hello-world/blob/master/src/ra...

3 – Outputs: https://github.com/FlowStacks/hello-world/blob/master/src/ra...

4 – Example Job Tasks to Perform (States) https://github.com/FlowStacks/hello-world/blob/master/src/ra...

5 – Sample Twitter Job: https://github.com/FlowStacks/social-workflow/blob/master/sr...

6 – Redis Job Integration https://github.com/FlowStacks/hello-world/blob/master/src/ra...

7 – Postman https://news.ycombinator.com/item?id=7615365

Great tool we use during development of our REST APIs. Liking the collections for testing regressions too.

Our Startup can help other Startups build an MVP

We're a startup that can help you get to your MVP faster by handling your back end for you. We streamline new feature development via a new type of REST API. We're trying to improve and expand our technology, but need real world use cases to do this. By working with your startup directly, we'll be able to do that while providing personal customization and functionality that you need...

( Read More... | 7 comments | 14 points | on HN )