Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I am developing an iOS app with SwiftUI but I am having issues with AdMob banners.
While developing and testing the ads I used the test AppID and AdUnitID, and all is working correctly. The banner ad shows up correctly in the simulator and when I run locally on my iPhone.
I then set the AdMob AppID and AdUnitID to my own (not the test ones) to submit my app to the App Store. When people download my app from the App Store, the banner just shows blank.
I created my AdUnitID in AdMob almost a week ago, but the banners are still showing up blank.
Any suggestions on what I could be missing or doing wrong? Thanks!
In Google AdMob is your app linked to the App Store?
I have 3 apps in the App Store. None have ads. I have test ads appearing in a new dev version of one of my Apps. The previous version has been in the App Store for over a week.
Via Google Admob when I search for the App in the App Store it does not find it. It is able to find my other two Apps that have been in the App Store for a longer period of time.
I'm waiting to be able to link the App to AddMob before I put the new version in the App Store.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
TL;DR
Is it smart to have a website that shall go into production ~July be developed with Flutter for Web considering Flutter-based mobile apps may follow 2021?
Preface:
I am planning website project and will start looking for a developer this week to build an MVP. I know I want Django for the backend, but frontend-wise I am not so sure.
Its my first larger website project and I am not really familiar with different frontend technologies.
I guess I need to trade off between cheaper implementation of an MVP that I need to check if the idea could finance itself and something that is more expensice upfront that could last longer.
In the long run, if the MVP is successful, I could imagine having native web as well. Flutter seems to be a very interesting framework to minimize development cost. However, initially it will be web only and Flutter is only in beta phase there.
The options I see are:
Django backend and frontend (maybe with some Angular/React/Vue directly inside the Django Templates)
Django backend + Django REST Framework + Angular/React/Vue frontend
Django backend + Django REST Framework + Flutter Frontend (hoping it will be stable enough by summer)
Actual Questions:
Can asking a developer to build a website now that shall go into
production in summer (i. e. it doesn't have to work perfectly fine
immediately, July or so would be enough) with flutter as frontend
really be an option?
Is it likely at all Flutter for Web will become
stable enough by then?
What would be the effort to transfer a
Angular/React/Vue website to a flutter website later on?
Will looking for a Flutter Web developer who also can do Django limit me too much?
(i. e. it seems to me most developers know either Angular/React/Vue
but much fewer know Flutter, let alone Flutter Web)
I think I am eligible to answer this question as I am currently working on these techs (Flutter, Django, Angular, etc.). So I am assuming you want to start the development in the next two weeks.
My One-Line suggestion would be not to go with Flutter until your first priority is a mobile app.
There is still uncertainty about the stable release of Flutter Web and it's not confirmed if the Flutter team is going to release the stable release of Flutter Web by next year's summer. I have done POC with it and still find it unstable for production release as it has many issues. Flutter's official website itself does not suggest you deploy it in production for the web. You can read it here
If any developer starts development with Flutter for a website now, the developer can face many issues in the development and may not find some features which you want the website to have. So it's not mature enough right now to develop a website for production.
If you want an app then you can go with Flutter without any second thought. Many companies and startups are using it for production. You can check here
So it's very unlikely to be production-ready for Flutter-Web by July'21. You can check the milestones for Flutter here and I think it will take 0.5 to 1 year after the stable release of Flutter to be production-ready for the web.
To answer your third question, I need to know the complexity of the website. Probably you can start with AngularDart and it can reduce migration efforts in the future.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
Im new to web development and trying to learn APIs through Django Rest Framework. I am actually confused about why we actually need to build an API. For example, I've seen tutorials of creating blog APIs, where it returns the posts and its info. Why would we need an API for that? We can simply create regular Django views to do the same. I've heard that APIs only provide the 'data', but I can also obtain data from regular Django. So why would you install a totally new 'sub' framework to do these for you?
Suppose you want to build a mobile application that serves some blog posts. have you thought about how you are going to fetch the blog posts from a back-end.
Take the case of instagram, the app fetches images,comments and tags from the django backend in the form of json data and can display relevant data on the application. in short, APIs can be used when the backend and frontend technologies are different and they can communicate through APIs
The biggest reason to use Django REST Framework is because it makes serialization so easy!
see this medium post
https://medium.com/#BennettGarner/build-your-first-rest-api-with-django-rest-framework-e394e39a482c
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
I have written a service using C++ and Qt framework (QtService). The service should run in the background. I need the service to have a web user interface and can be accessed using web browsers. I mean the service should act as as a web server and output html content to a specific port. I know there are some frameworks that can be used to generate web content in C++, but by taking into account that I am using Qt, I prefer to use Qt features as much as possible rather than a new framework. Any ideas?
I have read about Cutelyst on the Qt blog a few times, which seems an exact fit to your question.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I'm trying to develop a web application in Django including a REST API and also a web application to allow user to login and see stuff. I'm a bit confused as to how these are connected together.
I'm thinking that Django ORM is at the bottom and on top of that comes the API and then the web app uses the API to generate HTML. Is this correct understanding? A yes or no with few {key}words explanation would be enough.
What is the best practice?
Basically Django ORM is the bottom layer in your app as it will make possible to manipulate your data. When it comes to APIs, the main goal is to make accessible and manipulable your data from different devices (clients), for instance your web app and your iOS app may consume the same API and that will reduce your implementation time and eventually it will give you a better integration through your different clients and devices. Last but not least, the Web app is at this point the consumer to your API and your front-end.
You could check Tastypie or Django REST framework/ in order to implement your API and for your web app you have plenty of frameworks that you could use as Backbone, AngularJS etc.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am working on a web application project. This web application will have many users, and each user will be able to upload images to the website. Then I will write an android application to access those images. This is the description of my project.
Should I go with single page application such as backbone.js or should i go with a multi-page application approach such as Django? For the database stuff, I was thinking of going with Mongodb for now. Any advice on that is very appreciated !
Thanks,
An SPA (single page app) has nothing to do with going with Django or Backbone. You can write an SPA while using Django. BUT you can also use Backbone along with Django. For more on this, read these posts:
http://sidazad.tumblr.com/post/52201957429/web-2-0-the-switch-to-client-javascript-frameworks
http://sidazad.tumblr.com/post/52591790157/the-search-for-the-perfect-software-stack-part-1
To answer your question, I'd say use Backbone + Django and go with a Single Page App. That's where the web is moving. By using Backbone as well as Django you will get the advantages that Django provides on the server side while getting the great client side code organization and plumbing for a SPA from Backbone.
There are ways in which you can write your django templates so they are reusable on the client side. Look at this project in my GitHub for help with this on which I will be writing a post soon:
https://github.com/sidazad/django-backbone-stack-1