Exactly. The idea of an app is cool, but it doesn't work with the current system of posting mixes on blogs. You need a browser to access the hosting/download sites.
Brainstorming other ideas... I was thinking that having an IMDB-style website with a top 500 mixes would be cool. But I haven't seen a Wordpress theme that is specifically built for that yet. The Roots Archives website also has a nice organizational system.
I feel like our aggregate collection of mixes could use a better (and centralized) archiving system. And it would be nice if it had local hosting to reduce the maintenance.
I'm down to create a joint site archiving all of our mixes depending on the hosting costs. Pipo's Castle? Dirtymixes? However, creating some sort of phone app or finding a way to share mixes via smart phone is the future. For the time being, creating a soundcloud account and following my favorite mixes works as a poor man's phone app.
I think it's important to distinguish the difference between an "app" and a "website". In my opinion, a website also falls under the general category of an "application". But obviously there are some differences between most phone apps and websites.
I think it's important to understand that, in our case, a mobile-friendly website is more appropriate than an "app" (a term which means different things to different people).
Most phone "apps" are created for specialized (and often unique) tasks. They are more akin to the types of "apps" that we have on our more traditional computers to perform mostly local tasks.
Websites were created to accomodate and standardize social interactions amongst numerous people on ALL devices that have a browser.
A mobile-friendly website can be just as easy to access as an app, it is cheaper to develop, it will probably remain compatible for a longer period of time, it will be easier to add features without doing custom code, and its architecture will enable it to be highly social and interactive.
The only problem with websites on phones is that most developers have not been optimizing their CSS for phones. I can say from experience that rewriting the CSS to work on a phone is a hell of a lot easier than developing a highly interactive, database-driven phone "app".
Also, if we did an "app", we would still need a website too, right? So as I see it we should just build a website that covers all devices.
I'm just not sure what features an app would have that a website would not.
Good points. You're right, what I'm really looking for is a mobile phone friendly site layout with all the appropriate functionality for hosting mixes.
Email me when you get a chance and we can talk about this idea in further detail.
10 comments:
Wicked mix. Thanks Pipo. How many Dj's do that james brown lynn colins mix!!??
Its a Bboy standard that
When is pipomixes coming out with an iphone app?
hmmmm... good idea. But expect a droid app before an iphone one. I use droid
any programers looking to do pro-bono work? Not exactly pro-bono, I can pay in mixes.
thinking about it a little more, twitter and the soundcloud app works in theory as well as a pipomixes app would.
Exactly. The idea of an app is cool, but it doesn't work with the current system of posting mixes on blogs. You need a browser to access the hosting/download sites.
Brainstorming other ideas... I was thinking that having an IMDB-style website with a top 500 mixes would be cool. But I haven't seen a Wordpress theme that is specifically built for that yet. The Roots Archives website also has a nice organizational system.
I feel like our aggregate collection of mixes could use a better (and centralized) archiving system. And it would be nice if it had local hosting to reduce the maintenance.
I'm down to create a joint site archiving all of our mixes depending on the hosting costs. Pipo's Castle? Dirtymixes? However, creating some sort of phone app or finding a way to share mixes via smart phone is the future. For the time being, creating a soundcloud account and following my favorite mixes works as a poor man's phone app.
Cool, man. That's good to hear!
I think it's important to distinguish the difference between an "app" and a "website". In my opinion, a website also falls under the general category of an "application". But obviously there are some differences between most phone apps and websites.
I think it's important to understand that, in our case, a mobile-friendly website is more appropriate than an "app" (a term which means different things to different people).
Most phone "apps" are created for specialized (and often unique) tasks. They are more akin to the types of "apps" that we have on our more traditional computers to perform mostly local tasks.
Websites were created to accomodate and standardize social interactions amongst numerous people on ALL devices that have a browser.
A mobile-friendly website can be just as easy to access as an app, it is cheaper to develop, it will probably remain compatible for a longer period of time, it will be easier to add features without doing custom code, and its architecture will enable it to be highly social and interactive.
The only problem with websites on phones is that most developers have not been optimizing their CSS for phones. I can say from experience that rewriting the CSS to work on a phone is a hell of a lot easier than developing a highly interactive, database-driven phone "app".
Also, if we did an "app", we would still need a website too, right? So as I see it we should just build a website that covers all devices.
I'm just not sure what features an app would have that a website would not.
Good points. You're right, what I'm really looking for is a mobile phone friendly site layout with all the appropriate functionality for hosting mixes.
Email me when you get a chance and we can talk about this idea in further detail.
Post a Comment