| |
In lugnet.cad, Travis Cobbs wrote:
> In lugnet.cad, Orion Pobursky wrote:
> > In lugnet.cad, Paul Sinasohn wrote:
> > > Does anyone know of any efforts to build an LDraw display app for the iPad or
> > > any Android system?
> >
> > Not that I'm aware of. The biggest issue I can think of is how to handle the
> > library. I think the best way would be to convert it to a binary format and
> > update the app every time a new parts update is released.
>
> I own a 4th-gen iPod Touch, and I even have an iPad at work, so I've considered
> it. I think it could be done for the iPad/iPhone/iPod Touch. In fact, I could
> see a pared-down LDView running there quite happily. The library could be a
> simple zip file (either unzipped during the first run or simply left in zip
> format depending on how that performed).
>
> However, publishing such an app would require somebody to spend $100 per year on
> an iOS developer account, and I'm not personally willing to do that.
>
> --Travis Cobbs
I'd be willing to front the iOS developer fee in partnership with someone, but I
really don't want to have to learn how to program...
Anyone interested?
We could charge a buck for the finished app to get back the developer fee...
Paul
|
|
| |
In lugnet.cad, Paul Sinasohn wrote:
> In lugnet.cad, Travis Cobbs wrote:
> > However, publishing such an app would require somebody to spend $100 per year on
> > an iOS developer account, and I'm not personally willing to do that.
> >
> > --Travis Cobbs
>
> I'd be willing to front the iOS developer fee in partnership with someone, but I
> really don't want to have to learn how to program...
>
> Anyone interested?
>
> We could charge a buck for the finished app to get back the developer fee...
I'd be interested, but I should warn you that I'm unsure about the ability of an
LDraw viewer to sell 145 copies at $.99 each, which is how many would have to
sell to recoup the $100. (If I was highly confident of the market, I'd do it
all myself.) Also, I would likely need artwork help from someone. My
understanding is that the app approval process could fail if the artwork is too
bad, and I'm definitely no artist.
--Travis Cobbs
|
|
| |
In lugnet.cad, Travis Cobbs wrote:
| |
LDraw viewer to sell 145 copies at $.99 each, which is how many would have to
sell to recoup the $100.
|
Okay, explain to me (in layman terms) what you are talking about here. If it is
anything remotely related to ldraw and LEGO, hell, I’d pay the .99 to support
the effort!
JOHN
|
|
| |
In lugnet.cad, John Neal wrote:
| |
In lugnet.cad, Travis Cobbs wrote:
| |
LDraw viewer to sell 145 copies at $.99 each, which is how many would have
to sell to recoup the $100.
|
Okay, explain to me (in layman terms) what you are talking about here. If it
is anything remotely related to ldraw and LEGO, hell, I’d pay the .99 to
support the effort!
|
It would be an LDraw viewer for iPhone/iPad/iPod Touch. If I wrote it, it would
be based on LDView (and presumably be called LDView), but would have a
simplified UI appropriate to the iOS touch interface. It would be available on
the Apple App Store.
--Travis
|
|
| |
In lugnet.cad, Travis Cobbs wrote:
| |
In lugnet.cad, John Neal wrote:
| |
In lugnet.cad, Travis Cobbs wrote:
| |
LDraw viewer to sell 145 copies at $.99 each, which is how many would have
to sell to recoup the $100.
|
Okay, explain to me (in layman terms) what you are talking about here. If it
is anything remotely related to ldraw and LEGO, hell, I’d pay the .99 to
support the effort!
|
It would be an LDraw viewer for iPhone/iPad/iPod Touch. If I wrote it, it
would be based on LDView (and presumably be called LDView), but would have a
simplified UI appropriate to the iOS touch interface. It would be available
on the Apple App Store.
--Travis
|
Could you team up with Ace Kim from fbtb.net who has already created an app?
http://itunes.apple.com/us/app/bricking-news/id398355004?mt=8
That would save the $100 cost, sell for $.99 or even $1.99?
Just a thought.
I’d buy one.
Chris Eyerly
|
|
| |
In lugnet.cad, Chris Eyerly wrote:
Thanks for the suggestion. The answer would depend on two things:
- Whether or not Ace and I could come to an agreement.
- Whether or not Ace has a company. Joint iOS development requires proving to Apple that there is an actual company involved. Otherwise, only one person can do development.
--Travis
|
|
|
