> On Sep 24, 2015, at 4:40 AM, Marc Kaufmann <marc.kaufman...@gmail.com> wrote: > > Hi all, > > I am about to start writing an app. Really all it will have to do (for now) > is to give the user a bunch of survey questions at several times (per day or > week or whatever). It does matter quite a bit that it should work on both > Android and iOS (and Windows phones, if it it must). For further background, > I've never written an app in my life, but have worked on a bunch of websites. > I am good enough at it to know that I am not particularly good at web design.
This has nothing to do with Racket per se, but have you considered simply delivering your app as a web page? This advice would have saved me literally hundreds of programmer-hours if I’d heeded it a year ago. Also (and perhaps surprisingly), it is generally a *lot* easier to get something that looks decent using HTML/CSS than developing a native app. (Students insisted on native app, spent all year working on it, then I threw it away & did it in a week as a web app.) Best, John Clements > > My questions are these: > > • I found a thread in February about Racket, and it seems to be the > case that the Racket runtime compiles to Android, but not to iOS (or only > with very careful configuration and crossing one's fingers). Is that correct? > • What does it mean in practical terms that only the runtime compiles > to it? Or, to quote, that "the Racket runtime system at least compile[s] as a > framework for iOS (as it does already for Android)". What is missing in terms > of functionality, both on the users' side and the developers? > • Is there any open source code out there from someone who has written > an app in Racket (even if generating HTML5 and JS) so that I can get a sense > of what is a sensible way of going about this? The second best would be > pointers to good GUI programming in Racket. > • Would people caution against using Racket for this at this stage - > i.e. is there a high chance I'll spend a much larger fraction of my time > chasing down errors related to portability than would be the case with > alternatives? Since I want to get things working on Android and iOS, I might > have these problems with most solutions. > My main reason for wanting to use Racket is that I don't want to learn > another language (and be mediocre at it yet again) if I can avoid it, and the > only other languages I can code in without internet connection are Python and > R. R would be rather original as an app programming language. > > Thanks, > > Marc > > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
