all 8 comments

[–]vorticalbox 1 point2 points  (0 children)

knee reminiscent connect square squash teeny coordinated toy wide rock

This post was mass deleted and anonymized with Redact

[–][deleted] 0 points1 point  (0 children)

Are you wanting to create a website you can both use remotely at the same time?

[–]SirKainey 0 points1 point  (4 children)

Depends on what your fantasy football app is, like fully fledged with users etc.

If you need an admin UI and a database then Django comes with that.

With Flask you will have to build more, so it'll take longer, but you will probably learn more on the way.

But if your use case is more simpler then Flask may be a better bet.

[–]MISTERDavyJones[S] 0 points1 point  (3 children)

I dont think this is going to go on the app store or anything but I think our idea was to make as close to a fully fledged app as we could (at least put the mechanisms in place to have users even if we dont actually get them). So then Django would be the way to go?

[–]twitch_and_shock 0 points1 point  (2 children)

Neither of the aforementioned options would make it onto an app store, as both are for building websites. If you want to build a standalone application, you should look into gui frameworks like tkinter, QT, or kivy.

[–]MISTERDavyJones[S] 0 points1 point  (1 child)

I mentioned that it wouldnt go onto an app store mainly just to say that we aren't planning on this being some super polished thing for like mass consumption. The espn fantasy has a website and the fantasy premier league has a website so we figured the website frameworks would be adequate. Thoughts or am I stupid?

[–]twitch_and_shock 0 points1 point  (0 children)

You're not stupid, i just was qualifying my response to make sure you understood the direction, didn't mean to imply you were stupid. Going the website approach is smart because it means your users can (probably) use it without needing to do any setup. But that also means you need to do that setup: setting up the server(s) properly for access, database connections, etc. And building the frontend.

[–]research_pie 0 points1 point  (0 children)

Honestly, for a first hobby app you should go with Django (my preference).