Hacker Newsnew | comments | show | ask | jobs | submit | diegogcouto's comments login

I'd like to congratulate you, not only for your app (that is pretty nice) but for being open to criticism and help a lot of new developers making your app open.

Thanks!

-----


Thank you! I wouldn't have gotten anywhere in coding without open source and the communities around it, so it would be poor form not to try and give something back. Hopefully I'll contribute slightly more elegant code in the future :).

-----


Maybe with your video it'll be clear, but just looking to your layout, I can't understand what you're going to do, so there isn't any motive to "tell you" my email.

So, I suggest you to, with few words, describe what's your purpose. You're going against an app? Which app? Why? What are you going to do?

-----


First, I'd like to say that you've made a very good job! My suggestions (I'll try to focus on things that haven't be already suggested):

* Try to get rid of this image slider. It's difficult to pay attention with this huge thing moving.

* Your logo is a button equals to other buttons on your page. It's quite confusing to me.

* Try to work with tables only when you're really want to make use of a table and not as a way to organize your layout. You'll find out that this approach will help you to save a lot of time to maintain your website.

* Make use of standard icons: I saw some icons in 3D and others that are really similar to "cliparts".

-----


It's good to know the point of view of another WP developer, so thank you for your feedback!

I've also worked with WordPress and, as I said, it's really a very nice product, but it's not as user friendly as it should be and it probably won't change in any near future, because its user base already is used to work with it as it is.

My experience with WordPress showed me that for both, users and developers, it could be really easier to work with.

I made some experiments with some of my clients who use WP, and the Pareto's principle was king here, I mean, 80% of all the actions made use of 20% of the features.

I agree with you when you say that there are a lot of big players working on a minimalist approach. But I really think that there are a lot of users who really want to own their data. If you make a fast search about people incentivizing another's to get their own blog with their own domain, you'll see that maybe there's some market here.

I've never heard of KickPress, so I'll study it, but I got really impressed with HappyTables!

Thanks again for you comments. They're pretty useful!

-----


It's a very interesting point!

I'm focused to make all the process easier (and the WP admin panel is full of boring stuff, in my opinion), so maybe the creation of the whole product could be a natural evolution of the plugin instead of a new product.

The plugin could also help me to attract users, adding some functionalities to WordPress blogs and making available an option to move to my product, with even more features.

-----


Your feedback was really important to make me think about which kind of user I should focus initially.

First, I was thinking how to get attention of the regular user, but you made me think about how it could be a lot more useful to developers and designers in a first moment.

Your idea is awesome, I'm very grateful for your help!

-----


No problem. If you build it and it grows, then you have to hire me as a engineer. :)

In all seriousness, the trick to this kind of platform is the following. You have to make it very, very easy to work with. Using confusing API calls will just make people run away from it. I've seen a lot of APIs that are over engineerd with wacky syntax. Try and keep it as simple as possible, as if the developer was writing HTML itself.

The only problem with wordpress is the platform itself. In order to build something with it, you are accepting a lot of engineering overhead from past versions. This technical baggage makes it a pain to work it, though not as bad as joomla. By going with the API route, you can change the back end as much as you'd like, but the developers would just see the same API calls. Its like an interface in OOP programming.

The last API I did for a client took calls like this:

host/category/products/product/id/get

to this:

host/get/id

See how easier it is to develop with that? You dont need to know what category the product belongs to, because that data is passed as a JSON string to you. Once you get it, on your side you just go through the results and display it accordingly.

Same with a blog API. I dont need to know the title, just the post ID. So do host/get/id and then in the front end do {% post.title %} {% post.author %}{% post.date_published %} {% post.content %}

and so on.

-----


First of all, thanks for your feedback!

It's really important to know the experiences of people that already worked on this area, I'll consider everything that you've said.

How it's important to me to store my thoughts and my work on my own server, I though that improving the process of blogging and bringing some social features (taking care with noise problems) would be nice to everyone.

It's really a naive approach, I know, because as you also have said, Tumblr is very powerful now and it's free.

Probably I won't get attention of the usual Tumblr user in the beginning, so I'll bet on the developers and designers, with a simple to use app for their clients and easy to work and customize (as orangethirty brilliantly suggested).

What you think about it?

Thanks again!

-----


It's different because it's a powerful approach, I think.

Doing this, I'll make every blog open to a lot of different applications to interact with it's content.

By example, a user will be able to comment on an article published on a blog he "follows" from his own page.

-----


I'm very interested about it too.

A non-hosted web app can be easily copied, and the solution that I've found to this issue was to bet on crowdfunding to develop and make profit with services.

Now I'm preparing the ideas to launch and as soon as I get some usefull information I'll update it.

-----


I agree with you and it's a very interesting point, but I also think that there is another one.

Let's suppose that you're developing some tool that could solve problems of a lot of people. It's natural that you try to sell this to them (there isn't free lunch).

Getting paid only by services, in my opinion it's not that sustainable, because you'll have costs with this service and you already have other costs with development. To start making some profit, the price of the service has to be high.

-----


Applications are open for YC Winter 2016

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: